Re: Git migration - Mailing list pgsql-odbc

(2013/04/16 5:00), Heikki Linnakangas wrote:
> I finally got a copy of the CVS repository (thanks Marc Fournier!), and
> got to try the git migration using cvs2git. That produces better results
> than the built-in git-cvsimport tool I used earlier.
>
> I pushed the result to github for review:
>
> https://github.com/hlinnaka/psqlodbc-migration
>
> Please take a look!
>
> I used the following mapping of CVS usernames to Git authors:
>
> author_transforms={
>     'anoop' : ('Anoop Kumar', 'anoopk@pervasive-postgres.com'),
>     'bmomjian' : ('Bruce Momjian', 'bruce@momjian.us'),
>     'byronn' : ('Byron Nikolaidis', 'byronn@insightdist.com'),
>     'dpage' : ('Dave Page', 'dpage@pgadmin.org'),
>     'hinoue' : ('Hiroshi Inoue', 'inoue@tpf.co.jp'),
>     'h-saito' : ('Hiroshi Saito', 'hiroshi@winpg.jp'),
>     'peter' : ('Peter Eisentraut', 'peter_e@gmx.net'),
>     'scrappy' : ('Marc G. Fournier', 'scrappy@hub.org'),
>     'tgl' : ('Tom Lane', 'tgl@sss.pgh.pa.us'),
>     'thomas' : ('Thomas G. Lockhart', 'lockhart@fourpalms.org'),
>     'ishii' : ('Tatsuo Ishii', 'ishii@postgresql.org'),
>     'luf' : ('Ludek Finstrle', 'luf@pzkagis.cz'),
>       }
>
> I grabbed the email addresses from the pgfoundry developer list, and
> from recent postings from the authors, and from the similar list that
> was used in the main PostgreSQL repository conversion. Please check your
> own email address and spelling of your name, and let me know if you want
> to use something else.>
> I used the attached script to compare the tips of all the CVS branches
> and tags with the corresponding branches and tags in git. The only
> difference I found was this:
>
> ##### Comparing REL-08_02_0500 #####
> diff -u -N -r -x CVS /tmp/gitver/psqlodbc.h psqlodbc/psqlodbc.h
> --- /tmp/gitver/psqlodbc.h      2007-09-21 09:36:28.000000000 +0300
> +++ psqlodbc/psqlodbc.h 2013-04-15 22:32:44.094382349 +0300
> @@ -5,7 +5,7 @@
>     *
>     * Comments:           See "notice.txt" for copyright and license
> information.
>     *
> - * $Id: psqlodbc.h,v 1.121 2007/12/26 13:28:36 hinoue Exp $
> + * $Id: psqlodbc.h,v 1.120 2007/06/02 05:32:19 hinoue Exp $
>     *
>     */
>
> ##### end comparison #####
>
> I'm not sure why that happened, but I think that's acceptable as the
> difference is only in the $Id$ CVS keyword.
>
> Also, cvs2git created a few "manufactured" commits, where branches and
> tags have been created. Like this:
>
> commit 0b63b2ec3a5f80f20d7982a13c6255bd6a239887
> Author: cvs2svn <cvs2svn>
> Date:   Thu Jun 30 09:30:39 2005 +0000
>
>       This commit was manufactured by cvs2svn to create branch 'PRE_LIBPQ'.
>
> Most of them are actually quite pointless, as the commits don't change
> any files. We could remove them, but they're harmless and not too ugly,
> so I'm inclined to just leave them as is.
>
> So, here's my proposal on how to proceed with this:
>
> 1. Create a new official git repository at git.postgresql.org for the
> project, called "psqlodbc".
>
> 2. Copy the repository that I pushed to github for review to
> git.postgresql.org.
>
> 3. After the migration, perform one commit on master branch to remove
> CVS keywords from all files.
>
> Any objections? I could do this pretty much immediately, but should
> probably leave some time for people to review the repository and raise
> any comments. So, how about I do this on Friday, April 19th?

As Vadim pointed out, the CVS repository at http://pgfoundry.org/scm/
doesn't work. I think we had better migrate to Git ASAP.

regards,
Hiroshi Inoue