Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id DD1FE6342FF for ; Thu, 28 May 2009 14:01:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 56978-08 for ; Thu, 28 May 2009 14:01:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7C201632300 for ; Thu, 28 May 2009 13:52:09 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n4SGp6sm012043; Thu, 28 May 2009 12:51:06 -0400 (EDT) To: Alvaro Herrera cc: Robert Haas , Markus Wanner , Andrew Dunstan , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up In-reply-to: <20090528164401.GE5156@alvh.no-ip.org> References: <20090528020909.GQ15213@yugib.highrise.ca> <603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com> <20090528125944.GS15213@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> Comments: In-reply-to Alvaro Herrera message dated "Thu, 28 May 2009 12:44:01 -0400" Date: Thu, 28 May 2009 12:51:06 -0400 Message-ID: <12042.1243529466@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.119 tagged_above=0 required=5 tests=AWL=0.119 X-Spam-Level: X-Archive-Number: 200905/1281 X-Sequence-Number: 138823 Alvaro Herrera 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. regards, tom lane