Re: [Ipsec-tools-devel] NAT traversal broken

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 07/12/2014 01:29 PM, Rainer Weikusat wrote:
> it. The reason for this is that CVS is the only SCM I've found so
> far which has decent support for managing more than one
> independent project (I'm presenty maintaining or 'also/ mainly
> maintaining' 58 different 'private' Debian packages).

I'm not quite sure what this means.  It has been 10 years now since I
have touched CVS ( switched to subversion, which was leaps and bounds
better than CVS, though quite anachronistic by today's standards ),
but iirc, there was a MODULES definition section that let you define
multiple projects to be hosted in a single repository, is that what
you are referring to?

If so, how is that preferable to simply creating a different git repo
per project?  Git submodules can even be used to import one shared
project as a subdirectory into another while still maintaining them as
separate repositories with their own unique history.  Or if you want
you can simply create a different branch for each project and keep
them all in one repo and switch back and forth between them with git
checkout.

Colin Watson also recently wrote git-dpm, which is a great little
wrapper tool just for maintaining debian packages in git that makes it
a snap to track your own patches and periodically update to a new
upstream release.  It even automatically mirrors the git commits to
quilt patches so the source package still looks like a normal 3.0 (
quilt ) package to people not using git or git-dpm.  Using this I have
been managing a single git repo that contains both the upstream parted
git tree, as well as the debian package and I can move code around
between them easily, simultaneously pushing patches upstream and to
the debian package.