Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] pgsql: /home/peter/commit-msg

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: [HACKERS] pgsql: /home/peter/commit-msg
Date: 2009-11-16 17:05:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
On mån, 2009-11-16 at 10:05 -0500, Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> > Magnus Hagander wrote:
> >> On Mon, Nov 16, 2009 at 08:29, David Fetter <david(at)fetter(dot)org> wrote:
> >>> On Mon, Nov 16, 2009 at 06:56:54AM +0200, Peter Eisentraut wrote:
> >>>> Yeah, sorry guys.  I fixed the CVS log message now.
> >> So it's not only not strange, I'm very happy it didn't pull those
> >> changes and broke my repository :-)
> > Yeah, I'm glad it didn't do anything funny with the mirror.
> I think we should have a policy of NO manual changes to the CVS
> repository files.  At least not without careful discussion beforehand.

I used cvs admin.

In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2009-11-16 17:13:13
Subject: Re: Summary and Plan for Hot Standby
Previous:From: Chris BrowneDate: 2009-11-16 16:31:12
Subject: Re: next CommitFest

pgsql-committers by date

Next:From: Tom LaneDate: 2009-11-16 18:04:41
Subject: pgsql: While doing the final setrefs.c pass over a plan tree, try to
Previous:From: Tom LaneDate: 2009-11-16 15:05:54
Subject: Re: [HACKERS] pgsql: /home/peter/commit-msg

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group