Re: [PATCH] Teach git-svn how to catch up with its tracking branches

From: Steven Grimm <koreth@midwinter.com>
Date: May 8, 2008, 07:58 UTC
Message-ID: <604A38BB-E6A4-4303-BD7C-BF2968B6828D@midwinter.com>
In-Reply-To: <20080508074332.GB302@diana.vm.bytemark.co.uk>

On May 8, 2008, at 12:43 AM, Karl Hasselström wrote:

> Or even _only_ pull from the git repo. That repo would have to have
> some kind of hook to make sure that it's always up-to-date, then --
> just a cron job won't do -- but I'm sure that can be done.

If you control both the svn repo and the git repo, you can get close to that with an svn commit trigger, but even then there'll be a race condition when you want to dcommit. You either have to be able to pull from the svn repo when you want to dcommit, or you have to live with the possibility of a dcommit failing because you don't actually have the most recent rev locally.

This ties a bit into the patch I sent a few months back to allow update hooks to change refs. I kind of ran out of spare time to iterate more on that back then, but the ultimate goal there was that you could interact only with the bridge repo, never directly with svn, and the bridge repo would dcommit for you when you pushed to it.

The approach in this thread's patch is maybe not as conceptually clean, but it's much simpler and (apparently) less controversial.

-Steve