@@ -9,11 +9,11 @@ git-subtree - Merge subtrees together and split repository into subtrees
9
9
SYNOPSIS
10
10
--------
11
11
[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>]
17
17
18
18
19
19
DESCRIPTION
@@ -34,9 +34,9 @@ work. A subtree is just a subdirectory that can be
34
34
committed to, branched, and merged along with your project in
35
35
any way you want.
36
36
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
38
38
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
40
40
entire history of a subdirectory from your project and make it
41
41
into a standalone project. Unlike the subtree merge strategy
42
42
you can alternate back and forth between these
0 commit comments