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 <normalper...@yhbt.net> Signed-off-by: Johan Herland <jo...@herland.net> --- > 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=<regex>;; When passed to 'init' or 'clone' this regular expression will be preserved as a config key. See 'fetch' for a description -- 22.214.171.1247.g6ba9303 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html