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

Re: PostgreSQL Developer meeting minutes up

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Markus Wanner <markus(at)bluegap(dot)ch>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: 2009-05-28 16:54:29
Message-ID: 603c8f070905280954m72823478u87366e32f9bc7d5e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, May 28, 2009 at 12:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> There's another issue which is that of the $Id$ and similar tags.  We
>> have to decide what we want to do with them.  If we're not going to have
>> them in the Git repository, then they are only causing trouble right now
>> and it would be better to get rid of them completely for the conversion,
>> to avoid the noise that they will invariably cause.
>
> What was in the back of my mind was that we'd go around and mass-remove
> $PostgreSQL$ (and any other lurking tags), but only from HEAD and only
> after the repo conversion.  Although just before it would be okay too.
> The stickier part of this is what to do about back branches;
> particularly whether we are okay with checked-out versions of past
> releases not matching the actual shipped tarballs on this point.

Mass-deleting these tags from HEAD and the current head of each
back-branch seems like a good place to start.

...Robert

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2009-05-28 16:58:04
Subject: Re: Clean shutdown and warm standby
Previous:From: Tom LaneDate: 2009-05-28 16:51:06
Subject: Re: PostgreSQL Developer meeting minutes up

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