Re: Moving to git
От | Dave Cramer |
---|---|
Тема | Re: Moving to git |
Дата | |
Msg-id | CADK3HHKD+KqvA=3VnUnPRruTHvnmbQPGFhBBfMA9xDW-r92uNw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Moving to git (Kris Jurka <books@ejurka.com>) |
Ответы |
Re: Moving to git
|
Список | 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@ejurka.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc >
В списке pgsql-jdbc по дате отправления: