| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CVS commit messages and backpatching |
| Date: | 2006-09-13 21:16:54 |
| Message-ID: | 16816.1158182214@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:
> I guess the question is whether it is possible using cvs2cl to show only
> HEAD, and then show if the same commit message also appears in the most
> recent back branch.
It's so rare that we make a back-branch patch without a corresponding
HEAD patch that I'm not clear why you are concerned about showing only
HEAD for this purpose. I've always found that cvs2cl's behavior shows
me exactly what I want to know for CVS log searching (and that includes
release note making). If the output format isn't quite what you want,
maybe you could turn on its XML-output option and then munge that into
HTML. I've never had occasion to play with the XML-format option myself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-13 21:18:33 | Re: Lock partitions |
| Previous Message | Bruce Momjian | 2006-09-13 21:14:57 | Patch attribution and non-ASCII characters |