Re: cvs to git migration - keywords - Mailing list pgsql-hackers

From Dave Page
Subject Re: cvs to git migration - keywords
Date
Msg-id AANLkTilfFbPYXOToh1Jw1Yz8DuCWMOePt4TQRKzDx6a5@mail.gmail.com
Whole thread Raw
In response to Re: cvs to git migration - keywords  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jul 7, 2010 at 3:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> One point that isn't completely clear from Magnus' description is
> whether we should remove the $PostgreSQL$ lines from the HEAD branch
> only, or from the still-active back branches as well.  I vote for the
> latter --- that is, if you pull a historical version of some file
> from the archives, you should see the appropriate $PostgreSQL$ line,
> but we won't have them in the source files for any future minor
> release.  The reason for this is that otherwise there will be files
> floating around that claim to be CVS version x.y.z, but actually are
> different from that, because of back-patching activity after the git
> transition.  That seems like a recipe for huge confusion in itself.

Agreed. They should be removed from the active back branches.


--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: cvs to git migration - keywords
Next
From: Robert Haas
Date:
Subject: Re: cvs to git migration - keywords