Re: Add .gitignore files to CVS?

From: Roger Leigh <rleigh(at)codelibre(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add .gitignore files to CVS?
Date: 2010-01-09 20:57:56
Message-ID: 20100109205755.GA30889@codelibre.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 09, 2010 at 12:47:00PM +0100, Magnus Hagander wrote:
> On Sat, Jan 9, 2010 at 05:54, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > Tom Lane escribió:
> >> David Fetter <david(at)fetter(dot)org> writes:
> >> > On Fri, Jan 08, 2010 at 10:35:24PM -0500, Tom Lane wrote:
> >> >> Probably eventually we'll be on git and this will be moot, but that
> >> >> doesn't seem to be ready to happen.
> >>
> >> > What still needs to happen on this?  Clearly this would be a post-8.5
> >> > (or whatever the new release number is) thing, but apart from that?
> >>
> >> AFAIR, we still weren't convinced that we had a 100% conversion method
> >> (ie something that would preserve all the history) and there were still
> >> questions about how to work with multi-branch patches most effectively.
> >> I don't recall where the previous discussion died off exactly, but
> >> it definitely wasn't at the "we're ready to do it" stage.
> >
> > Somebody did a pull of all the tags, and some of them were missing files
> > and failed to build.
>
> That was from the current git mirror.
>
> To re-itarate yet again, what I believe has been said many times before:
>
> There are two ways to get from cvs to git.
>
> The first one is reliable (at least from what I've heard). But it only
> supports one-off migrations. It doesn't support incremental changes.
> It was confused by some things that were plain broken in our cvs
> repository way back (this happens with cvs, as we all know), but AFAIK
> they have been fixed.

As a git user who has now done a number of CVS->git migrations over the
past few years, I also found that the various tools to do the
conversion do have their own issues (such as cvsps) which can lead to
incorrect history in some corner cases. Unfortunately, in any big
repo with a lot of history, you do tend to find you trip up on them
in a few places.

My experience was that the CVS->SVN conversion tended to be rather
more reliable and accurate. As a result, going GIT->SVN->git can
give a much better history. At least in my experience.

Regards,
Roger

--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-01-09 21:01:07 Re: damage control mode
Previous Message Dean Rasheed 2010-01-09 20:53:54 Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function