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

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

From
Sebastian Leske <sebastian.leske@sleske.name>
Date
Nov 30, 2012, 07:16 UTC
Message-ID
<ce1aae1a3130b92e2253ce1d737036980ee8a67a.1354324110.git.Sebastian.Leske@sleske.name>
In-Reply-To
<cover.1354324110.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 |    7 +++++++
 1 file changed, 7 insertions(+)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 6bda014..18d5e45 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -959,6 +959,13 @@ 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.
 
+SVN tags (if tracked using options '--tags' or '--stdlayout') are
+imported as git branches, prefixing the tag name with 'tags/'.
+This is because tags in SVN behave more like git branches: The contents
+of a tag need not be identical to the tagged commit, and 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).
+
 CONFIGURATION
 -------------
 
-- 
1.7.10.4
Previous: Junio C HamanoNext: Sebastian Leske
Message 6 of 10 in “git-svn: More docs for branch handling in”
  1. 0/4 git-svn: More docs for branch handling inSebastian Leske, Dec 1, 2012
  2. 1/4 git-svn: Document branches with at-sign(@).Sebastian Leske, Nov 30, 2012
  3. Junio C HamanoDec 3, 2012
  4. 2/4 Recommend use of structure options for git svn.Sebastian Leske, Nov 30, 2012
  5. Junio C HamanoDec 3, 2012
  6. 4/4 git-svn: Note about tags.Sebastian Leske, Nov 30, 2012
  7. 3/4 git-svn: Expand documentation for --follow-parentSebastian Leske, Nov 30, 2012
  8. Junio C HamanoDec 3, 2012
  9. Junio C HamanoDec 3, 2012
  10. Eric WongDec 4, 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.