John Ralls jra...@ceridwen.us writes:
I'd use flock -n. There's no need for a job to wait when another is
going to come along in a minute anyway. Move the rm inside the lock
and check the lock (without the -n) in the commit hook to prevent a
race between clearing, setting, and processing.
John Ralls jra...@ceridwen.us writes:
On Mar 25, 2013, at 8:39 AM, Derek Atkins warl...@mit.edu wrote:
Perhaps I should set up a cron job to flush it out every 6 hours, just
in case something missed?
Can't hurt. Would it be reasonable to have a kicker like the one for
ceridwen, but in
On Mar 26, 2013, at 8:00 AM, Derek Atkins warl...@mit.edu wrote:
John Ralls jra...@ceridwen.us writes:
On Mar 25, 2013, at 8:39 AM, Derek Atkins warl...@mit.edu wrote:
Perhaps I should set up a cron job to flush it out every 6 hours, just
in case something missed?
Can't hurt. Would
On Mar 26, 2013, at 8:43 AM, John Ralls jra...@ceridwen.us wrote:
On Mar 26, 2013, at 8:00 AM, Derek Atkins warl...@mit.edu wrote:
John Ralls jra...@ceridwen.us writes:
On Mar 25, 2013, at 8:39 AM, Derek Atkins warl...@mit.edu wrote:
Perhaps I should set up a cron job to flush it
John Ralls jra...@ceridwen.us writes:
We'll (I'll ;-) ) have to add some error handling to the push_repo
function in git-svn-mirror (you're still using that, right?) to make
it die if the push fails. Then your cron script can just test it and
re-touch if it fails.
Alternatively, push_repo
Hi,
On Tue, March 26, 2013 12:56 pm, John Ralls wrote:
OK. Forward the emails and we can discuss which ones merit handling inside
of git-svn-mirror, which can be ignored, and which require human
intervention, then set up error handling accordingly. There should
probably be a limit on the
On Tue, March 26, 2013 2:24 pm, John Ralls wrote:
[snip]
It's perhaps a bit more involved than what you need because it has to
decide which repo to update. You also might prefer to get emails than to
use syslog.
Okay, I've added a lock so it should handle the case of back-to-back
commits. I
On Mar 26, 2013, at 11:49 AM, Derek Atkins de...@ihtfp.com wrote:
I'm trying to understand why you use two locks, but I think it's because
the first lock is used as the trigger and the second lock is used to make
sure only one copy runs at a time. So yes, I can add a proc lock in
there to
Mike Alexander m...@umich.edu writes:
Is the mechanism that pushes changes from SVN to GIT not working
right? I checked in a change nearly 5 hours ago which shows up in SVN
(it's r22832) but it hasn't appeared in the GIT repository yet. I
checked it in using git svn dcommit as usual and
On Mar 25, 2013, at 8:39 AM, Derek Atkins warl...@mit.edu wrote:
Perhaps I should set up a cron job to flush it out every 6 hours, just
in case something missed?
Can't hurt. Would it be reasonable to have a kicker like the one for
ceridwen, but in reverse, so that if it doesn't work right
On Sun, 24 Mar 2013 10:55:47 +
Mike Evans mi...@saxicola.idps.co.uk wrote:
On Sun, 24 Mar 2013 00:52:25 -0400
Mike Alexander m...@umich.edu wrote:
Is the mechanism that pushes changes from SVN to GIT not working right?
I checked in a change nearly 5 hours ago which shows up in SVN
Is the mechanism that pushes changes from SVN to GIT not working right?
I checked in a change nearly 5 hours ago which shows up in SVN (it's
r22832) but it hasn't appeared in the GIT repository yet. I checked it
in using git svn dcommit as usual and everything looked normal.
Mike
12 matches
Mail list logo
