Skip site navigation (1) Skip section navigation (2)

Re: Problem in GIT mirror (was Re: pgsql: Fix all the server-side SIGQUIT handlers ...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-www(at)postgresql(dot)org
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all the server-side SIGQUIT handlers ...)
Date: 2009-05-16 19:13:25
Message-ID: 4718.1242501205@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-www
David Fetter <david(at)fetter(dot)org> writes:
> On Sat, May 16, 2009 at 01:51:59PM +0200, Magnus Hagander wrote:
>> Does anybody know of a better way to fix it, without this happening?

> Not sure exactly, but the nice people at
> <http://repo.or.cz/w/PostgreSQL.git> appear to be managing not to have
> this problem.  What say we look into how they're doing theirs? :)

Or they've just been lucky (so far).

But if this was a case of the git mirror seeing the commit as non
atomic, I don't understand why it wouldn't have later picked up the
rest of the changes as a separate commit with the same message.
Seems like you'd have to work at it to prevent that from happening
... maybe there is some heuristic for identifying "a single commit"
that goes horribly wrong here?

			regards, tom lane

In response to

pgsql-www by date

Next:From: Bruce MomjianDate: 2009-05-17 13:19:45
Subject: spam email from pgfoundry
Previous:From: David FetterDate: 2009-05-16 17:31:39
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)

pgsql-committers by date

Next:From: Tom LaneDate: 2009-05-16 20:43:46
Subject: pgsql: Improve comments in pg_ident.conf.sample.
Previous:From: David FetterDate: 2009-05-16 17:31:39
Subject: Re: Problem in GIT mirror (was Re: pgsql: Fix all theserver-side SIGQUIT handlers ...)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group