Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Date: 2010-12-29 04:39:32
Message-ID: AANLkTi=4BOuFLOzCSxt4ddoZf+mbbcSFJ57y57Gn3Ly6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Dec 28, 2010 at 11:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
>
> 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. Consider:

git cherry-pick -n master
# hack
git commit -a

Or:

git cherry-pick master
# check it, then, if needed, make and fold in modifications:
git commit -a --amend --date=now

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2010-12-29 04:48:31 Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
Previous Message Tom Lane 2010-12-29 04:02:29 pgsql: Avoid unexpected conversion overflow in planner for distant date