Content-Type: text/plain; charset=UTF-8
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thom Brown <thom@linux.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: CVS in docs
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Magnus Hagander <magnus@hagander.net>
In-reply-to: <AANLkTimSMgvG_zgDyD3mc68g0sR6jzySo_wbRUHf=u=u@mail.gmail.com>
References: <AANLkTimJVWSegpzD7ywO8S6AHfg8doQOVXQDem6xhkhc@mail.gmail.com>
	<10904.1285108697@sss.pgh.pa.us>
	<AANLkTi=K+NS7g5g=Z++eheA2A+5uLEPTmLsBq8ULGukA@mail.gmail.com>
	<26043.1285169700@sss.pgh.pa.us>
	<AANLkTimSMgvG_zgDyD3mc68g0sR6jzySo_wbRUHf=u=u@mail.gmail.com>
Date: Wed, 22 Sep 2010 13:53:53 -0400
Message-Id: <1285177724-sup-6812@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

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