Hello, * On Thu, Feb 17, 2005 at 09:45:40AM -0700 Mark E. Hamilton wrote: > 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?
This is correct. > ><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. Not necessarily. If you are operating from a machine that uses CR/LF (for example, Windows), than the CR/LF was converted on check in, thus, the repository version is corrupted, too. > 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? If you are working from Unix boxes solely, this works as expected. If not, chances are you have to check in a new binary file. Regards, Spiro. -- Spiro R. Trikaliotis http://cbm4win.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs