Re: Report: removing the inconsistencies in our CVS->git conversion - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Report: removing the inconsistencies in our CVS->git conversion
Date
Msg-id AANLkTikUafNdxsc+kxw48Q5Xaa58fHuZQ6ud2CoDQzVO@mail.gmail.com
Whole thread Raw
In response to Re: Report: removing the inconsistencies in our CVS->git conversion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Sep 17, 2010 at 23:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Actually, the simplest way to handle this might be to just delete all
> five of those tags during the conversion, and then I'll put them back
> in the right places later when I add the other old-release tags.
> That way we won't have any tags getting moved after the repository is
> published.  (Or am I wrong about that being something to avoid?  But
> in any case we want to gc the manufactured commits for Release_2_0_0
> and Release_2_0.)

As long as nobody has cloned the repository, it's not a problem moving
them. But it *is* something you should generally avoid, so let's do
that :-)


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Report: removing the inconsistencies in our CVS->git conversion
Next
From: Joseph Adams
Date:
Subject: Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)