[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] polished git repo

From: Kamil Dudka
Subject: Re: [Nano-devel] polished git repo
Date: Tue, 16 Feb 2016 11:59:23 +0100
User-agent: KMail/4.14.10 (Linux/4.3.5-300.fc23.x86_64; KDE/4.14.16; x86_64; ; )

On Tuesday 16 February 2016 04:48:20 Mike Frysinger wrote:
> i've spent some time doing an automated/hand conversion of the svn repo
> to git.  a plain conversion doesn't work for a few reasons:
>  - trunk/ contains a nano/ subdir instead of being in trunk/
>  - some branches/ also contain a nano/ subdir, but not all
>  - same goes for tags/
>  - some of the converted tags would pick the wrong base rev and generate
>    a big commit to sync to the tag state
>  - some of the svn tags were bad (created multiple times)
> so after doing a conversion of trunk/nano/ as the master branch, i did
> conversions for each branch/ (making sure they synced with trunk), and
> located all the tags in the git history to match them up.  i checked the
> content against the original svn and it looks good, and did a spot check
> of some tarball releases, but only a few.
> the only two outstanding issues:
>  - the converted git does not do include keyword expansion (e.g. $ID:$),
>    so many of the files will not diff exactly to the tarballs.  git does
>    not make this easy, so i think it's fine to leave as-is.
>  - the git messages all have the svn metadata in them.  e.g. the log has:
>    git-svn-id: svn://
> 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 i think it's OK to leave these in.

Both of them are expected and harmless IMO.

> so with all that said, you can find the repo here:
>       git://
> or view it online here:

Good job.  Thanks for sharing!


> it's set up such that i can continue to import new versions from svn.
> it's not like we need to put a halt on svn dev and pick git right now.
> -mike

reply via email to

[Prev in Thread] Current Thread [Next in Thread]