RE: [Plib-devel] PLIB developers needed.

[Vallevand, M. K <Mar...@UN...>]

This is almost what I did!
The difference is that when I checked out the files again under
my userid using cvs/ssh, I only checked out the three files that
were being changed.  And, I only committed the three files that
were changed.  Could this make a difference?

If I commit *all* of plib, is cvs clever enough to only commit
the files that are actually changed?

Regards.
Mark K Vallevand   ma...@rs...
Never try and teach a pig to sing: it's a waste of time, and it annoys
the pig.

> I'm unclear what the problem is.
> 
> I have write access to a sourceforge project and I want to be 
> able to switch
> between anonymous CVS and CVS writing.
> 
> I want to use anonymous CVS when I'm updating my tree, but 
> CVS writes when
> checking something into the tree.
> 
> At the top level of the tree, I can do the following to 
> update my tree:
> cvs 
> -d:pserver:ano...@cv...:/cvsroot/quake update
> 
> And the following to do writes (with CVS_RSH set to ssh):
> cvs -d...@cv...:/cvsroot/quake commit
> 
> Once I do the write, I can do the former to reset CVS/Root to be the
> anonymous version.  It's just that simple when your CVS tree 
> isn't deep, but
> it gets more complicated when you have a deep hierarchy.  If 
> you are only
> operating from the root, you are fine with this scenario.   If you are
> running cvs commands from other directories, you'd have to 
> use the cvs update
> command in those directories to fix up CVS/Root
> 
> Loring