From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Thu, 28 May 2009 12:54:29 -0400
Message-ID: <603c8f070905280954m72823478u87366e32f9bc7d5e@mail.gmail.com> (raw)
In-Reply-To: <12042.1243529466@sss.pgh.pa.us>
References: <20090528020909.GQ15213@yugib.highrise.ca>
<603c8f070905280649m5d5fc458se54435dfe20cc7ca@mail.gmail.com>
<4A1E9D98.7030208@dunslane.net>
<8547.1243522369@sss.pgh.pa.us>
<20090528174015.964447it00chy25b@mail.bluegap.ch>
<603c8f070905280846q46220e39u57fc24ac7b6feb7@mail.gmail.com>
<20090528181016.20761ewel8xikmzs@mail.bluegap.ch>
<603c8f070905280921h1f8a59bahf6122abfbb2a4ef6@mail.gmail.com>
<20090528164401.GE5156@alvh.no-ip.org>
<12042.1243529466@sss.pgh.pa.us>
On Thu, May 28, 2009 at 12:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@commandprompt.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: robertmhaas@gmail.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, markus@bluegap.ch, andrew@dunslane.net, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <603c8f070905280954m72823478u87366e32f9bc7d5e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox