Johan Herland <jo...@herland.net> wrote: > On Tue, Oct 1, 2013 at 6:07 AM, Eric Wong <normalper...@yhbt.net> 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 thinking that if you run git svn init/clone without > --prefix, there should be a verbose warning explaining (a) the trouble > you're likely to encounter when using no prefix, and (b) the upcoming > change in default prefix. Obviuosly, there should be a corresponding > note in the git-svn manual page. Any other places in git.git that > warrants changing? Hopefully this should be sufficient to trigger > corresponding adjustments in third-party tools + docs ahead of the > actual change in 1.9/2.0.
Probably, yes. I don't remember off the top of my head if there's other places, but init/clone should be a good enough start. -- 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