Re: Fwd: Error with git-svn pushing a rename
- From
- Benjamin Pabst <benjamin.pabst85@gmail.com>
- Date
- Nov 20, 2013, 22:10 UTC
- Message-ID
- <CAM-uYMiLpsQdN41Gs8iJOT-v0qKgod2vEeoC3C+QJ5+wKiVK-Q@mail.gmail.com>
- In-Reply-To
- <52894951.7000303@futurelab.ch>
Hi,
is it possible to debug git-svn or get a more verbose / debug output from it? I already tried with the "GIT_TRACE" variable, but it does not include any further output on the svn methods.
Regards, Benjamin
2013/11/17 Andreas Stricker <astricker@futurelab.ch>:
Show 18 quoted lines
> Hi Jonathan > >> Can you give an exact sequence of steps (including "Upgrade Subversion >> at this step") to reproduce the problem? That would help immensely >> --- if at all possible, I would very much like to keep existing >> git-svn repos working on upgrade. > > Of course. I've attached a text file with the commands required to > reproduce this error. > > From my experiments it looks like after the subversion is upgraded > to 1.8 the problem only occurs if "git svn fetch" fetches new changes > from the subversion repository. Without changes in upstream subversion > repository I couldn't reproduce the error. And a rename is required too. > > Hope this helps. > > Regards, Andy