Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ...
| От | Robert Haas |
|---|---|
| Тема | Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ... |
| Дата | |
| Msg-id | AANLkTi=4BOuFLOzCSxt4ddoZf+mbbcSFJ57y57Gn3Ly6@mail.gmail.com обсуждение исходный текст |
| Ответ на | pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ... (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in
8.3 or 8.2 ...
Re: pgsql: Ooops, no DATE_IS_NOBEGIN/DATE_IS_NOEND in 8.3 or 8.2 ... |
| Список | pgsql-committers |
On Tue, Dec 28, 2010 at 11:02 PM, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-committers по дате отправления: