git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 3/4] git-svn: Expand documentation for --follow-parent

From
Sebastian Leske <sebastian.leske@sleske.name>
Date
Nov 23, 2012, 07:13 UTC
Message-ID
<a9748faec2a18231ad588c1a2dedb82e74685d74.1353691892.git.Sebastian.Leske@sleske.name>
In-Reply-To
<b115a546fa783b4121d118bb8fdb9270443f90fa.1353691892.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 |   16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 928a961..92780ef 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -628,11 +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 (i.e. branched) 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
-	--no-follow-parent to disable it.
+	that has been moved around within the repository (note that you
+	must track both the old and the new name for the whole history
+	to be imported).  If this feature is disabled, the branches
+	created by 'git svn' will all be linaear and not share any
+	history, meaning that there will be no information on where
+	branches where branched off or merged. This feature is enabled
+	by default, use --no-follow-parent to disable it.
 +
 [verse]
 config key: svn.followparent
-- 
1.7.10.4
Previous: Michael J GruberNext: Michael J Gruber
Message 4 of 8 in “git-svn: Document branches with at-sign(@).”
  1. 1/4 git-svn: Document branches with at-sign(@).Sebastian Leske, Nov 18, 2012
  2. 2/4 Recommend use of structure options for git svn.Sebastian Leske, Nov 21, 2012
  3. Michael J GruberNov 28, 2012
  4. 3/4 git-svn: Expand documentation for --follow-parentSebastian Leske, Nov 23, 2012
  5. Michael J GruberNov 28, 2012
  6. 4/4 git-svn: Note about tags.Sebastian Leske, Nov 23, 2012
  7. Michael J GruberNov 28, 2012
  8. Michael J GruberNov 28, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.