From: Jon Seymour <jon.seymour@gmail.com>
To: "Matěj Cepl" <mcepl@redhat.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn troubles with calendarserver SVN repo
Date: Mon, 2 Dec 2013 18:00:54 +1100 [thread overview]
Message-ID: <CAH3Anroi65OrZZQ0MvmPxgWZXB_eG=1aA-cxqdR=y-uAXsFaNA@mail.gmail.com> (raw)
In-Reply-To: <529C229F.2030504@redhat.com>
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 <mcepl@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: mcepl@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.
>
next prev parent reply other threads:[~2013-12-02 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 23:14 git-svn troubles with calendarserver SVN repo Matěj Cepl
2013-11-30 8:54 ` Jon Seymour
2013-12-02 6:03 ` Matěj Cepl
2013-12-02 7:00 ` Jon Seymour [this message]
2013-12-02 11:01 ` Ramkumar Ramachandra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH3Anroi65OrZZQ0MvmPxgWZXB_eG=1aA-cxqdR=y-uAXsFaNA@mail.gmail.com' \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcepl@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).