> Now, I already have all my sources in CVS here on my machince, and looking
> through the CVS docs I have here, I have not found anything on how to keep
> _two_ repositories "current" without running into problems (maybe it's so
> simple that they didn't even consider it worth mentioning).

This is likely possible, but undoubtably tricky...

> My hope is that something like this will work: I change my CVSROOT and
> CVS_RSH settings and then simply do a commit from my local working
directory
> into the sourceforge CVS.

If you have updated files you want to import, here's how I'd do it:

Check out the project from SF CVS into in a temporary directory.

Copy your updated files over the SF CVS version.

Do a commit from your SF CVS directory.

> I'd just go ahead and try, but cleaning up a messed up import on CVS can
be
> a hassle. As you can probably tell by now, my knowledge about CVS is
rather
> limited - I know the basics (how to commit/checkout files and resolve
> conflicts), but that's it.

The above procedure is as safe as doing a normal commit, but you loose any
intermediate info in your existing CVS archive.

I just use the SF CVS for everything, and don't bother with a local CVS
repository.  Unless you're on a *REALLY* slow connection, the updates
shouldn't take long (CVS is pretty responsive, even tunneled through ssh on
my pitiful Pentium-90 based Debian development system)...any particular
reason you're using a local repository instead of the SF CVS server?

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)


_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to