Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ... - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Date
Msg-id 4D1AC091.6020508@dunslane.net
Whole thread Raw
In response to Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers

On 12/28/2010 11:50 PM, Tom Lane wrote:
> Robert Haas<robertmhaas@gmail.com>  writes:
>> On Tue, Dec 28, 2010 at 11:02 PM, Tom Lane<tgl@sss.pgh.pa.us>  wrote:
>>> I heard the siren call of git cherry-pick, but should have lashed myself
>>> to the mast.
>> Applying the same patch blindly to every branch can bite you no matter
>> how you move the patch around.
> Sure.  But git cherry-pick encourages you to commit first and test
> later, which is how come I ended up with a commit I couldn't undo.
> Think I'll use -n in future.
>


Would not git reset have undone the faulty commit if necessary?

cheers

andrew

pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...