git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Sebastian Leske <Sebastian.Leske@sleske.name>
To: git@vger.kernel.org
Cc: Eric Wong <normalperson@yhbt.net>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 4/4] git-svn: Note about tags.
Date: Fri, 23 Nov 2012 08:29:38 +0100	[thread overview]
Message-ID: <ad8d146e958494bacde498cedc2d17020db65f1e.1354693001.git.Sebastian.Leske@sleske.name> (raw)
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

  reply	other threads:[~2012-12-05 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  7:36 [PATCH v3 0/4] git-svn: More docs for branch handling Sebastian Leske
2012-11-23  7:29 ` Sebastian Leske [this message]
2012-11-30  7:16 ` [PATCH v3 3/4] git-svn: Expand documentation for --follow-parent Sebastian Leske
2012-11-30  7:16 ` [PATCH v3 1/4] git-svn: Document branches with at-sign(@) Sebastian Leske
2012-12-05 19:27   ` Junio C Hamano
2012-12-05 21:27     ` Eric Wong
2012-11-30  7:16 ` [PATCH v3 2/4] git-svn: Recommend use of structure options Sebastian Leske

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ad8d146e958494bacde498cedc2d17020db65f1e.1354693001.git.Sebastian.Leske@sleske.name \
    --to=sebastian.leske@sleske.name \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).