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

[PATCH v3 4/4] git-svn: Note about tags.

From
Sebastian Leske <sebastian.leske@sleske.name>
Date
Nov 23, 2012, 07:29 UTC
Message-ID
<ad8d146e958494bacde498cedc2d17020db65f1e.1354693001.git.Sebastian.Leske@sleske.name>
In-Reply-To
<cover.1354693001.git.Sebastian.Leske@sleske.name>
Document that 'git svn' will import SVN tags as branches.
Signed-off-by: Sebastian Leske <sebastian.leske@sleske.name>
---
 Documentation/git-svn.txt |    6 ++++++
 1 file changed, 6 insertions(+)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 021fb0e..445b033 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -968,6 +968,12 @@ the possible corner cases (git doesn't do it, either).  Committing
 renamed and copied files is fully supported if they're similar enough
 for git to detect them.
 
+In SVN, it is possible (though discouraged) to commit changes to a tag
+(because a tag is just a directory copy, thus technically the same as a
+branch). When cloning an SVN repository, 'git svn' cannot know if such a
+commit to a tag will happen in the future. Thus it acts conservatively
+and imports all SVN tags as branches, prefixing the tag name with 'tags/'.
+
 CONFIGURATION
 -------------
 
-- 
1.7.10.4
Previous: Sebastian LeskeNext: Sebastian Leske
Message 2 of 7 in “git-svn: More docs for branch handling”
  1. 0/4 git-svn: More docs for branch handlingSebastian Leske, Dec 5, 2012
  2. 4/4 git-svn: Note about tags.Sebastian Leske, Nov 23, 2012
  3. 1/4 git-svn: Document branches with at-sign(@).Sebastian Leske, Nov 30, 2012
  4. Junio C HamanoDec 5, 2012
  5. Eric WongDec 5, 2012
  6. 2/4 git-svn: Recommend use of structure options.Sebastian Leske, Nov 30, 2012
  7. 3/4 git-svn: Expand documentation for --follow-parentSebastian Leske, Nov 30, 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.