Re: [COMMITTERS] pgsql: pgindent run for 9.0, second run - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [COMMITTERS] pgsql: pgindent run for 9.0, second run
Date
Msg-id AANLkTimBEeeO5BLAVDXkXcty_mmLkRmjmVmJpcrhJWul@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: pgindent run for 9.0, second run  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Tue, Jul 20, 2010 at 18:32, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Robert Haas <robertmhaas@gmail.com> wrote:
>
>> It would result in a massive merge commit and the duplication of
>> the entire history.
>
> Ah, well, if the two repositories don't share the same IDs, it a
> clear no-go.  Now that I think about it, it would be a bit much to
> expect those to match on independent conversions from CVS.
>
> How is this going to play out when we do the "official" conversion
> to git?  Will those of us on repositories based off of
> git.postgresql.org be faced with similar issues, or are we using the
> repo there as the base for the conversion?

No, it will be a completely new repository. Those with the old one
will need to extract a patch from that and then apply it to the new
one.

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


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: [COMMITTERS] pgsql: pgindent run for 9.0, second run
Next
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: pgindent run for 9.0, second run