[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 17 Aug 2001 17:32:46 -0700
Hmm, from the cvs output that you describe
(M) it looks like cvs just thought it was locally modified.
It didn't do a merge. That, to me, implies that cvs
thought the file was 'up-to-date' in your working copy, and
The thing I would have checked (before you had blown away the
file and re-did the update) - would have been the CVS/Entries
file and seen what version of startComponents.cfg
was listed in the Entries file.... if it was listing 1.3,
then at some point your working copy had already been updated.
If it listed 1.2, and cvs didn't do a merge on the update, then
that sounds like a bug....
From: Schwenk, Jeanie [mailto:address@hidden
Sent: Friday, August 17, 2001 5:05 PM
To: CVSpost (E-mail)
Cc: Kennedy, Dean
We've had a cvs update that didn't work. The file startComponents.cfg
version 1.2 was in my scripts directory. The scripts directory had been
checked out days before from the repository. Another user modified the
the file and checked it in (version 1.3). I did a cvs update and got
startComponents.cfg" but the file did not actually update.
In order to get the updated file, I had to delete the file in my
THEN do an update. Now I have the correct file.
Could it be a permissions problem? The scripts directory is wide open
the file had permissions rw-rw-r--. When I do an update, does the
run as me or as CVS? Could that be why it didn't update or is it
This is a serious issue and I need to understand what happened.
Info-cvs mailing list
- update, Schwenk, Jeanie, 2001/08/17
- RE: update,
Teala Spitzbarth <=
- RE: update, Teala Spitzbarth, 2001/08/18