My experience is that the fetch will be atomic - it either fetches an SVN commit or it doesn't.
Failure during dcommit is more painful and I usually find it is necessary to manually use a git rebase to rebase the commits that didn't make it to SVN on top of the commits that did. jon. On Mon, Dec 2, 2013 at 5:03 PM, Matěj Cepl <mc...@redhat.com> wrote: > On 30/11/13 09:54, Jon Seymour wrote: >> I have seen this behaviour, though never determined the root cause >> .Probably the simplest thing you can do without access to the server >> is to put your git svn fetch into a bash while loop, like so: >> >> while ! git svn fetch; do :; done; > > Of course, I did this, but still I wonder how much is the resulting git > repository http://luther.ceplovi.cz/git/CalendarServer.git/ faithful > representation of the original SVN one http://trac.calendarserver.org/. > Would not be something missing? > > Best, > > Matěj > > -- > http://www.ceplovi.cz/matej/, Jabber: mc...@ceplovi.cz > GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC > > They that can give up essential liberty to obtain a little > temporary safety deserve neither liberty nor safety. > -- Benjamin Franklin, Historical Review > of Pennsylvania, 1759. > -- 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
