[smc] Derek Scherger wrote:
[...]
> $ cvs update
> cvs update: Updating
> U file1
>
> $ mv file1.old file1
>
> After which cvs status knows about file1 and considers it modified or up
> to date depending on what was there in the first place.
>
> What about providing an option to checkout/update to enable this to be
> done automatically?
>
> Any comments or suggestions would be greatly appreciated!
[smc] CVS is actiing the way it acts ("move file1, it is in the
way", or whatever
the message is) on purpose. this is because file1 got there by
means other
than CVS, (i.e. you just created it fresh with an editor, or else
you copied it in
from someplace else manually.) It doesn't make sense for CVS to
consider
the file "modified" because it cannot assume that you mean for it to
be a
new version of the _same_ file. It must assume under these
circumstances
that it is a completely _different_ file that happens to have the
same name
as an already existing file. hence the mssage. Now, I have seen
(with older
versions of CVS) the CVS/Entries file get screwed up and CVS get
confused
and think that files that it created were such files. But I haven't
seen that in
a very long time (probably more than 1 year ago was the last time I
saw that,
and even then, I'm not sure the user wasn't doing something screwy,
like
editing CVS/Entries).
