diff options
author | Johan Herland <johan@herland.net> | 2013-10-11 14:57:07 +0200 |
---|---|---|
committer | Eric Wong <normalperson@yhbt.net> | 2014-04-19 11:30:13 +0000 |
commit | fe191fcaa58cb785c804465a0da9bcba9fd9e822 (patch) | |
tree | 34870aa374179b0300e0341899e7dee731a1ae1a /git-svn.perl | |
parent | cc291953df19aa4a97bee3590e708dc1fc557500 (diff) | |
download | git-fe191fcaa58cb785c804465a0da9bcba9fd9e822.tar.gz |
Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not given
git-svn by default puts its Subversion-tracking refs directly in
refs/remotes/*. This runs counter to Git's convention of using
refs/remotes/$remote/* for storing remote-tracking branches.
Furthermore, combining git-svn with regular git remotes run the risk of
clobbering refs under refs/remotes (e.g. if you have a git remote
called "tags" with a "v1" branch, it will overlap with the git-svn's
tracking branch for the "v1" tag from Subversion.
Even though the git-svn refs stored in refs/remotes/* are not "proper"
remote-tracking branches (since they are not covered by a proper git
remote's refspec), they clearly represent a similar concept, and would
benefit from following the same convention.
For example, if git-svn tracks Subversion branch "foo" at
refs/remotes/foo, and you create a local branch refs/heads/foo to add
some commits to be pushed back to Subversion (using "git svn dcommit),
then it is clearly unhelpful of Git to throw
warning: refname 'foo' is ambiguous.
every time you checkout, rebase, or otherwise interact with the branch.
The existing workaround for this is to supply the --prefix=quux/ to
git svn init/clone, so that git-svn's tracking branches end up in
refs/remotes/quux/* instead of refs/remotes/*. However, encouraging
users to specify --prefix to work around a design flaw in git-svn is
suboptimal, and not a long term solution to the problem. Instead,
git-svn should default to use a non-empty prefix that saves
unsuspecting users from the inconveniences described above.
This patch will only affect newly created git-svn setups, as the
--prefix option only applies to git svn init (and git svn clone).
Existing git-svn setups will continue with their existing (lack of)
prefix. Also, if anyone somehow prefers git-svn's old layout, they
can recreate that by explicitly passing an empty prefix (--prefix "")
on the git svn init/clone command line.
The patch changes the default value for --prefix from "" to "origin/",
updates the git-svn manual page, and fixes the fallout in the git-svn
testcases.
(Note that this patch might be easier to review using the --word-diff
and --word-diff-regex=. diff options.)
[ew: squashed description of <= 1.9 behavior into manpage]
Suggested-by: Thomas Ferris Nicolaisen <tfnico@gmail.com>
Signed-off-by: Johan Herland <johan@herland.net>
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Diffstat (limited to 'git-svn.perl')
-rwxr-xr-x | git-svn.perl | 12 |
1 files changed, 1 insertions, 11 deletions
diff --git a/git-svn.perl b/git-svn.perl index 7349ffea5a..0a323722a6 100755 --- a/git-svn.perl +++ b/git-svn.perl @@ -1389,17 +1389,7 @@ sub cmd_multi_init { usage(1); } - unless (defined $_prefix) { - $_prefix = ''; - warn <<EOF -WARNING: --prefix is not given, defaulting to empty prefix. - This is probably not what you want! In order to stay compatible - with regular remote-tracking refs, provide a prefix like - --prefix=origin/ (remember the trailing slash), which will cause - the SVN-tracking refs to be placed at refs/remotes/origin/*. -NOTE: In Git v2.0, the default prefix will change from empty to 'origin/'. -EOF - } + $_prefix = 'origin/' unless defined $_prefix; if (defined $url) { $url = canonicalize_url($url); init_subdir(@_); |