Re: Moving to git

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Mike Fowler <mike(at)mlfowler(dot)com>, Guillaume Cottenceau <gc(at)mnc(dot)ch>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Moving to git
Date: 2011-10-04 08:35:24
Message-ID: CADK3HHKD+KqvA=3VnUnPRruTHvnmbQPGFhBBfMA9xDW-r92uNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

So how does moving to git revolutionize the process ? I do understand
that CVS is ancient but what changes if we move to git ?

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Tue, Oct 4, 2011 at 3:03 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>
>
> On Tue, 4 Oct 2011, Craig Ringer wrote:
>
>> To what extent is *perfect* history reproduction required for PgJDBC?
>>
>
> Perfect history is not a requirement.  Largely because of the massive
> rewrite in the 8.0 timeframe there's not much utility in looking back much
> further.  Still, imperfect history better have a good explanation for its
> existence.  The server project had several suspect commits that they
> reconciled with their saved source trees rather than discarding.  I don't
> think the JDBC driver has nearly as many suspect commits, but I don't see
> why it would be hard to accurately import our history.
>
> My only caveat is for those who think git-cvsimport is adequate:
>
> http://archives.postgresql.org/pgsql-www/2008-12/msg00124.php
>
> Kris Jurka
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Andrew Hastie 2011-10-04 10:58:31 Re: OpenJPA problems running against PG 8.1
Previous Message Kris Jurka 2011-10-04 07:03:09 Re: Moving to git