Re: Policy decisions and cosmetic issues remaining for the git conversion - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Policy decisions and cosmetic issues remaining for the git conversion
Date
Msg-id 15148.1284398469@sss.pgh.pa.us
Whole thread Raw
In response to Re: Policy decisions and cosmetic issues remaining for the git conversion  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Policy decisions and cosmetic issues remaining for the git conversion  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Sep 13, 2010 at 12:50 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> +1 on both -- fixing the broken tags, and creating the missing tags,
>> particularly since you already seem to have found out the necessary
>> dates for the missing tags.

> +1 from me, too.  I don't agree with statements upthread that this
> will be "easier" to do in git.  I think we should fix the CVS history.
>  The git conversion is a one-time event.  Once it's done, history is
> set in stone.  We don't want to set the wrong thing in stone.

Well, the other side of that argument is that changing these things in
the CVS repository will be overwriting the available evidence, in case
any questions come up later.  On the git side, applying the tag to the
appropriate commit is an easy --- and easily changeable --- thing, isn't
it?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: Perf regression in 2.6.32 (Ubuntu 10.04 LTS)
Next
From: Tom Lane
Date:
Subject: Re: Report: removing the inconsistencies in our CVS->git conversion