Re: Git out of sync vs. CVS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Magnus Hagander" <magnus(at)hagander(dot)net>, "peter_e" <peter_e(at)gmx(dot)net>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git out of sync vs. CVS
Date: 2010-01-19 16:47:32
Message-ID: 11788.1263919652@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Oh, and what sort of delay do you feel would be "long enough to
> cover any cvs commit including potential network slowness during it
> etc."?

Why should the script make any assumptions about delay at all?
It seems to me that the problem comes from failing to check for
changed files, no more and no less. It would be much less of an
issue if a non-atomic CVS commit showed up as two separate GIT
commits with similar log messages.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2010-01-19 16:58:16 Re: ECPG patch 4.1, out-of-scope cursor support in native mode
Previous Message Tom Lane 2010-01-19 16:43:10 Re: Patch: Remove gcc dependency in definition of inline functions