Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> 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.)
I pull activity only from HEAD, so I do not see that tag. In fact, I use our src/tools/pgcvslog rather than cvslog. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
