Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7F3E1634ECC for ; Thu, 28 May 2009 14:25:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71281-07-4 for ; Thu, 28 May 2009 14:25:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f163.google.com (mail-bw0-f163.google.com [209.85.218.163]) by mail.postgresql.org (Postfix) with ESMTP id 9F79E634ACF for ; Thu, 28 May 2009 14:24:59 -0300 (ADT) Received: by bwz7 with SMTP id 7so5833142bwz.19 for ; Thu, 28 May 2009 10:24:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=X/CwicsLoOHHq0fy7TJgVOkGr6XmwalZ3sA+g3UaGUs=; b=P4wJdCXkiGKyDEhbQ9+Er1cO+HmVqLkRWu5+jddfdOuI/eSxo33faKAymfaSnl6LCZ ku7SfiVOdHKy207M5aslu0QYuQrgkb0sT70YKs5bhR4/qgD3xRHc6l//3t4tVc/0briu uxsBMP9WlmPzN6Tw2v08QkfdKTHfRYtvtMby4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RkLqIyCNmJp/nBiyAwKjhqXNW/V2yAuOM9gw5bVR8+eMDKYys2+jg0m2O+E5Ysnp/N 4jjeCyP66xsbfk9FMFKqqiyRyNpIwZ8qTnAx2ZFatq3GhbI6LwGBJIGKXur4IV9A0w2s YV0umlhamb+RkyhExMB+BzMcX/8LnZIFAs0V8= MIME-Version: 1.0 Received: by 10.204.77.78 with SMTP id f14mr1371220bkk.76.1243529669380; Thu, 28 May 2009 09:54:29 -0700 (PDT) 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> Date: Thu, 28 May 2009 12:54:29 -0400 Message-ID: <603c8f070905280954m72823478u87366e32f9bc7d5e@mail.gmail.com> Subject: Re: PostgreSQL Developer meeting minutes up From: Robert Haas To: Tom Lane Cc: Alvaro Herrera , Markus Wanner , Andrew Dunstan , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200905/1285 X-Sequence-Number: 138827 On Thu, May 28, 2009 at 12:51 PM, Tom Lane wrote: > Alvaro Herrera writes: >> There's another issue which is that of the $Id$ and similar tags. =A0We >> have to decide what we want to do with them. =A0If we're not going to ha= ve >> 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. =A0Although 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