Daniel Kahn Gillmor <[email protected]> writes:

> Niels, if you want to consider transitioning nettle sources out of the
> the lsh repository and into something like git (or any other dvcs), i'd
> be happy to help you do that.

I'm certainly considering it; it would be nice to get away from cvs. I
was involved in the conversion of the gmp repository to mercurial just a
few years ago. That was fairly easy, only serious obstacle was that we
discovered a rcs file where some early revision was corrupt. After
purging that broken revision with cvs admin, things worked well.

But to convert nettle and lsh, there are some issues:

1. I'm familiar with mercurial, but I hear that git is a better choice
   these days, so maybe I should go with git instead. And then I have
   some new stuff to learn.

2. Currently, several more-or-less independent projects are in the lsh
   cvs tree. Besides nettle, there's libspki, argp, sftp. So how should
   this be split up? As far as I understand, neither hg nor git have
   any well-working analogue to cvs modules, which would otherwise have
   been a natural choice.

   Also, I guess this splitting of the repository complicates migration
   a bit.

3. Then there's the shared files which are symlinked by the top-level
   lsh/.bootstrap script. I guess with a split it will be unavoidable to
   have multiple separately version controlled copies of those files.

I guess it's possible to start with migrating nettle from cvs, and leave
the rest of the tree for later. But I'm not sure that's a good way to do
it.

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.
_______________________________________________
nettle-bugs mailing list
[email protected]
http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs

Reply via email to