| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CVS commit messages and backpatching |
| Date: | 2006-09-13 17:43:46 |
| Message-ID: | 200609131743.k8DHhkv06370@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > FYI, in going through the release notes, I would like to remind
> > committers that it is important to mention if the commit was
> > backpatched to any earlier release.
>
> Backpatches usually happen after the commit to the head branch has been
> made, so the information is not available at that time.
Well, I have a script where I create a single commit message that I use
to apply to multiple branches. Usually you know at the time of commit
to HEAD that you are going to backpatch. And in such cases, it is
helpful to mention it as part of the HEAD commit.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2006-09-13 17:46:48 | Re: GIN documentation |
| Previous Message | Peter Eisentraut | 2006-09-13 17:30:20 | Re: CVS commit messages and backpatching |