David Fetter <david@fetter.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
