From: Johan Herland Date: Sat, 19 Apr 2014 09:10:31 GMT Subject: [PATCH] git-svn.txt: Retain a description og pre-v2.0 default prefix Message-ID: <1397898631-1585-1-git-send-email-johan@herland.net> In-Reply-To: <20140419083210.GA28771@dcvr.yhbt.net> Add a description of <=1.9 behavior in the manpage. Users on long-term-support systems are likely to continue using ancient git installations for some time (5-10 years, even?), but may come across the current documentation online. Suggested-by: Eric Wong Signed-off-by: Johan Herland --- > We should maintain a description of <=1.9 behavior in the manpage. > Users on long-term-support systems are likely to continue using ancient > git installations for some time (5-10 years, even?), but may come across > the current documentation online. Feel free to add/squash this on top. > Otherwise the patch looks fine and I can push it up for Junio for > 2.0-rc1. Thanks! ...Johan Documentation/git-svn.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt index 3a7dd80..5b3c38d 100644 --- a/Documentation/git-svn.txt +++ b/Documentation/git-svn.txt @@ -87,6 +87,11 @@ COMMANDS if you wish to track multiple projects that share a common repository. By default, the prefix is set to 'origin/'. ++ +NOTE: Before Git v2.0, the default prefix was "" (no prefix). This +meant that SVN-tracking refs were put at "refs/remotes/*", which is +incompatible with how Git's own remote-tracking refs are organized. + --ignore-paths=;; When passed to 'init' or 'clone' this regular expression will be preserved as a config key. See 'fetch' for a description -- 1.9.1.587.g6ba9303