| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Ray Stell <stellr(at)cns(dot)vt(dot)edu>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: 8.2.4 patches? |
| Date: | 2007-07-11 14:41:53 |
| Message-ID: | 25050.1184164913@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-www |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Alvaro Herrera wrote:
>> Hmm, do we include the cvs2cl-generated ChangeLog in the tarballs?
> No, we don't. We used to but the file got too large. Perhaps we should
> supply a URL that generates that information.
There are a couple of different queries that people would be interested
in:
* the full cvs2cl log between any two release points;
* the cvs2cl log from latest release to branch tip.
I do not think it's appropriate to stick this into the tarballs, as
there's an awful lot of noise in the logs (eg, docs tweaks, reverted
patches, trivial code cleanups); our practice of generating a condensed
release-notes page is a large public service in my eyes. But +1 to
providing a web page from which the detailed answers could be generated
easily.
BTW, cvs2cl (at least the version I use) works fine against a remote
repository, so it's not like Ray couldn't have gotten the answer for
himself. But a web page would be more user-friendly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-11 15:03:10 | Re: could not open relation 1663/16525/2604: no such file or dir |
| Previous Message | Chris Browne | 2007-07-11 14:23:24 | Re: linux os |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-07-11 16:21:03 | Re: [pgsql-advocacy] Front page image |
| Previous Message | Guillaume Lelarge | 2007-07-11 14:06:29 | Re: 8.2.4 patches? |