Re: CVS commit messages and backpatching

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CVS commit messages and backpatching
Date: 2006-09-13 17:58:05
Message-ID: 14787.1158170285@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> 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. Not only is this valuable for making the
> release notes, but it also helps people looking at the commit message.

With the standard output from cvs2cl, this is pretty obvious anyway, no?
I see entries like

2006-08-29 09:39 teodor

* contrib/tsearch2/: tsvector.c (REL8_1_STABLE), tsvector.c: Remove
pos comparison in silly_cmp_tsvector(): it is not a semantically
significant

so it seems to me that explicit mention of back-patching is mostly
redundant. (Of course, this requires the committer to commit all the
branches at about the same time, which I make an effort to do precisely
so that the cvs log looks nice. If some time elapses between patching
and back-patching then a mention in the commit message is definitely
needed.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-13 18:07:38 Re: - Proposal for repreparing prepared statements
Previous Message Strong, David 2006-09-13 17:52:26 Re: Lock partitions