summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Sebastian Leske <Sebastian.Leske@sleske.name>2012-11-23 08:29:38 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-12-27 15:38:26 -0800
commit008c208c2c54f7bb97bfb7bc5dc606a4eb0d6837 (patch)
treef05d9109c3bd8776149b61c8db61c7d95dfa5ff3
parentgit-svn: Expand documentation for --follow-parent (diff)
downloadtgif-008c208c2c54f7bb97bfb7bc5dc606a4eb0d6837.tar.xz
git-svn: Note about tags.
Document that 'git svn' will import SVN tags as branches. Signed-off-by: Sebastian Leske <sebastian.leske@sleske.name> Acked-by: Eric Wong <normalperson@yhbt.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-svn.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 84bff9b447..346f1b766f 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -960,6 +960,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
-------------