Hi Mike, 

> >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.
> 
> Don't do that. It will not work properly. 
Hmm, too bad. 

> Follow the instructions below,
> and let the SF staff know you want your repository placed in:
> leaf/devel/hejl
> 
> Importing existing CVS repositories
> https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1
> 
> When you submit the support request, please forward the request number to
> me. Thanks.
But wouldn't that mean that I move from my local one to SF (and therefore
should "close" my local repository)? At least, that's how I read the
document. I'm not really worried about losing the history (heck, I already
did that when I moved from the repository I maintained at my office to the
one I'm using now, at home, and I didn't bother (yet) with recreating at
least a history of the released versions). 

My goal with this is being able to use CVS locally, while at the same time
keeping the latest changes "public", without having to go through all the
double-checking I always need to when releasing a new version (if you look
at the lrpStat changelog, I'm sure you can spot where I _didn't_ do that
double-checking...)

> >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.
> 
> Cleaning up cvs problems is even harder for us. We don't have shell access
> to our repository.
That's what I thought, and mainly why I asked instead of just giving it a
try. I surely don't want to cause you any extra work. You do a great job at
managing this project, and I bet you have other things to do than to clean
up because somebody screwed up his CVS again...

> I hope the information above helps.
Indeed it does - even if I'm not sure that's the way I want to go. Maybe
just keeping a "development snapshot" tarball would be more effective?

Thanks for the feedback

Martin

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

Reply via email to