Re: [gnutls-dev] HAEDS UP: Moving away from CVS

[Simon Josefsson]

Florian Weimer <address@hidden> writes:

> * Simon Josefsson:
>
>> I have no idea what happens if I make any changes on the CVS server
>> though, although git-cvsimport claims to support that.
>
> Incremental conversion seems to work relatively well, especially if
> you haven't used broken CVS versions on your repository.
>
> Note that GIT has one drawback: it doesn't preserve file identity.
> Almost all other sytems (except CVS) keep file identity, which means
> that some manual work is necessary when you import GIT changesets into
> them.  The other way round is far easier.

Once I make the switch, I don't expect to import changesets back into
CVS actively.  However, one prerequisite for making the switch to git
is a read-only CVS mirror of the git repository (for people who want
to continue to use CVS), but if I understand correctly, git-cvsserver
takes care of that.  Or do these problems apply equally to
git-cvsserver?

> I believe the HTTP transport is a bit like a stepchild these days.
> And I couldn't clone your GIT repostory.

It seems to work fine here:

address@hidden:~/t$ git clone git://repo.or.cz/libtasn1.git
remote: Generating pack...
remote: Done counting 2312 objects.
remote: Deltifying 2312 objects.
remote:  100% (2312/2312) done
Indexing 2312 objects.
remote: Total 2312, written 2312 (delta 1572), reused 2312 (delta 1572)
 100% (2312/2312) done
Resolving 1572 deltas.
 100% (1572/1572) done
address@hidden:~/t$

Doesn't it work?

/Simon