Re: [RFC/PATCH] git svn: Set default --prefix='origin/' if --prefix is not given

Johan Herland wrote: > On Tue, Oct 1, 2013 at 6:07 AM, Eric Wong wrote: > > How about we put a big warning of impending change in there for now and > > wait until git 1.9/2.0 to make the actual change? > > Sounds sensible. What should the warning look like, and where should > it be placed? I'm t

Re: [RFC/PATCH] git svn: Set default --prefix='origin/' if --prefix is not given

On Tue, Oct 1, 2013 at 6:07 AM, Eric Wong wrote: > Johan Herland wrote: >> 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

Re: [RFC/PATCH] git svn: Set default --prefix='origin/' if --prefix is not given

Johan Herland wrote: > 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 > clobb

[RFC/PATCH] 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