Re: CVS in docs - Mailing list pgsql-docs

From Alvaro Herrera
Subject Re: CVS in docs
Date
Msg-id 1285177724-sup-6812@alvh.no-ip.org
Whole thread Raw
In response to Re: CVS in docs  (Magnus Hagander <magnus@hagander.net>)
Responses Re: CVS in docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: CVS in docs  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-docs
Excerpts from Magnus Hagander's message of mié sep 22 13:29:00 -0400 2010:
> On Wed, Sep 22, 2010 at 17:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Magnus Hagander <magnus@hagander.net> writes:

> >>     <!-- we need a file containing the CVS logs for each release, and something
> >>     like the SVN web interface that groups commits but has branches -->
> >
> > This comment should be updated, or deleted entirely.
>
> Given that I don't even understand what it means and what it does
> there, I deleted it :)

I think this is about having some sort of pointer to a ChangeLog or
similar resource (so that someone interested can see the commits for
each branch).  I didn't look at your patch, but if you provide a pointer
to the Git "summary", that seems enough.

BTW now that they are pestered with the PgFoundry commit messages, the
pgsql-committers archive do not seem a very useful resource anymore.
The Git "shortlog" seems much better, so maybe we should point to that.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-docs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: CVS in docs
Next
From: Tom Lane
Date:
Subject: Re: CVS in docs