Re: Info-cvs Digest, Vol 27, Issue 40

[Mark E. Hamilton]

David A. Bartmess wrote:
> When you added the files, did you specify "-kb" for the add command for the 
> binary jar files? If not, you'll have to change the status of the files using 
> the cvs admin command as follows:

> cvs update -A myJarFile.jar

Using 'update -A' will reset any sticky tags. What if his file is 
checked out from a branch? Wouldn't this get him the wrong working copy?

> <here, you need to copy the original jar file back over the sandbox version, 
> as the sandbox version is corrupted>
> cvs commit

Why would you need to do this? I thought that keywords were only 
expanded when the file was updated/checked-out/exported, so that the 
file in the repository should be okay; just the working version is 
corrupted.

The instructions I've given our users is to do this:

cvs admin -kb <file_name>
cvs update <file_name>

which has always seemed to work in the past. Are there situations where 
the repository file could be corrupted, so that this wouldn't work?

--
----------------
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666