| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "Massa, Harald Armin" <chef(at)ghum(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Alpha 1 release notes |
| Date: | 2009-08-13 15:08:44 |
| Message-ID: | 7386.1250176124@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> In any case, it is not the function of the alpha release notes to
>> discuss changes in earlier release branches. The reason the commit
>> log points out the back-patch is to make it easier to extract the
>> information when we prepare release notes for the back-branch updates.
> Hmm, isn't it enough to use cvs2cl --follow <branch>?
Yeah, cvs will certainly tell you the same information, which is why
I frequently don't bother mentioning the point at all in commit
messages. I think the most useful reason for mentioning the branch(es)
in a commit message is to explain why a particular patch goes back
so far and no farther.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-08-13 15:29:09 | Re: Hot standby and synchronous replication status |
| Previous Message | Alvaro Herrera | 2009-08-13 15:07:51 | Re: Filtering dictionaries support and unaccent dictionary |