Skip to content

Commit 9a40fcc

Browse files
committed
Fix a few typos/grammar-o's in the preceding commit.
1 parent 7f86ff0 commit 9a40fcc

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

Diff for: git-subtree.txt

+7-7
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ git-subtree - Merge subtrees together and split repository into subtrees
99
SYNOPSIS
1010
--------
1111
[verse]
12-
'git subtree' add -P <prefix>|--prefix=<prefix> <commit>
13-
'git subtree' pull -P <prefix>|--prefix=<prefix> <repository> <refspec...>
14-
'git subtree' push -P <prefix>|--prefix=<prefix> <repository> <refspec...>
15-
'git subtree' merge -P <prefix>|--prefix=<prefix> <commit>
16-
'git subtree' split -P <prefix>|--prefix=<prefix> [OPTIONS] [<commit>]
12+
'git subtree' add -P <prefix> <commit>
13+
'git subtree' pull -P <prefix> <repository> <refspec...>
14+
'git subtree' push -P <prefix> <repository> <refspec...>
15+
'git subtree' merge -P <prefix> <commit>
16+
'git subtree' split -P <prefix> [OPTIONS] [<commit>]
1717

1818

1919
DESCRIPTION
@@ -34,9 +34,9 @@ work. A subtree is just a subdirectory that can be
3434
committed to, branched, and merged along with your project in
3535
any way you want.
3636

37-
They are neither not to be confused with using the subtree merge
37+
They are also not to be confused with using the subtree merge
3838
strategy. The main difference is that, besides merging
39-
of the other project as a subdirectory, you can also extract the
39+
the other project as a subdirectory, you can also extract the
4040
entire history of a subdirectory from your project and make it
4141
into a standalone project. Unlike the subtree merge strategy
4242
you can alternate back and forth between these

0 commit comments

Comments
 (0)