Re: CVS Update Behaviour

[Paul Sander]

>--- Forwarded mail from address@hidden

>You're spreading F.U.D. and untruths again Paul.

Not with the stock version of CVS that I'm using.  Larry Jones has
already set me straight with regard to "cvs log" working properly
in the presence of a file that's been removed to the Attic in the
current release.

>[ On Friday, February 22, 2002 at 20:51:55 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour

>>  In this latter case, you need to
>> know where in the repository the RCS file sits, and that info isn't
>> usually available without some effort, particularly if the module isn't
>> defined trivially in the modules database.

>Yes it is.  It's in the commit message written automatically by
>something like my tiny simple little wrapper script.

Hmmm...  Let's recap:

>>      cp $1 $2
>>      cvs rm -f $1
>>      cvs add $2
>>      cvs commit -m "moved $1 to $2" $1 $2

Where is the *location of the RCS file* recorded in the comment?
Sure, the wrapper could read the CVS meta-data, but that's proprietary
to CVS and therefore not guaranteed to remain compatible in future
releases.

>> This exercise also doesn't consider the implications of doing the "cvs add"
>> part in a sandbox that has been updated with a different branch than the
>> original file.

>That's because doing such a stupid thing is outside the bounds of
>defined usage for CVS -- you really should only have one complete and
>coherent sandbox, all checked out on only one branch if you're using
>branches.  Anything and everything else may lead to undefined behaviour.

Yeah, well, users can be pretty ingenius when it comes to stuff like this.
The wrapper should at least look at the sticky tags of the workspaces to
make sure they're not doing something stupid.

>--- End of forwarded message from address@hidden