[PATCH v3 3/4] git-svn: Expand documentation for --follow-parent
- From
Sebastian Leske <sebastian.leske@sleske.name>
- Date
- Nov 30, 2012, 07:16 UTC
- Message-ID
- <3ebf48f71ec54fcec83f730c1cf6ec86c02d0677.1354693001.git.Sebastian.Leske@sleske.name>
- In-Reply-To
- <cover.1354693001.git.Sebastian.Leske@sleske.name>
Describe what the option --follow-parent does, and what happens if it is set or unset.
Signed-off-by: Sebastian Leske <sebastian.leske@sleske.name> --- Documentation/git-svn.txt | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt index d8e5082..021fb0e 100644 --- a/Documentation/git-svn.txt +++ b/Documentation/git-svn.txt @@ -628,10 +628,19 @@ ADVANCED OPTIONS Default: "svn" --follow-parent:: + This option is only relevant if we are tracking branches (using + one of the repository layout options --trunk, --tags, + --branches, --stdlayout). For each tracked branch, try to find + out where its revision was copied from, and set + a suitable parent in the first git commit for the branch. This is especially helpful when we're tracking a directory - that has been moved around within the repository, or if we - started tracking a branch and never tracked the trunk it was - descended from. This feature is enabled by default, use + that has been moved around within the repository. If this + feature is disabled, the branches created by 'git svn' will all + be linear and not share any history, meaning that there will be + no information on where branches were branched off or merged. + However, following long/convoluted histories can take a long + time, so disabling this feature may speed up the cloning + process. This feature is enabled by default, use --no-follow-parent to disable it. + [verse]
-- 1.7.10.4