| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Maintaining the list of release changes |
| Date: | 2002-02-16 05:36:45 |
| Message-ID: | 200202160536.AAA16831@www.wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 15 February 2002 08:43 pm, Peter Eisentraut wrote:
> Bruce Momjian writes:
> > Seems there are two uses for the CHANGES file, one is to enable
> > developers to see what has been added to the tree since they last
> > looked, best solved with cvslog,
> No, a cvslog is in nature different from a list of user-visible changes.
> We're not talking about the core group of developers here that read the
It almost sounds like you want something like BitKeeper, which, barring its
weird license, seems tobe just the ticker. But there's that weird license.....
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gordon A. Runkle | 2002-02-16 06:16:32 | Re: Odd statistics behaviour in 7.2 |
| Previous Message | Tom Lane | 2002-02-16 05:09:19 | Re: Ready to branch 7.2/7.3 ? |