If this was an 8.3 filenames related problem, the solution would be to copy
the files rather than move them. It looks as if, from your mail, cvs has the
correct long file names however. I think it's more likely that your problem
is that the two files have exactly the same modification time, and therefore
it doesn't look as if anything has changed when you replace one with the
other. I guess copying instead of moving would fix that problem as well.
Jerry
> From: Gerhard Sittig [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 12, 2000 12:15 PM
>
> On Tue, Jul 11, 2000 at 15:49 -0400, Dan Mindler wrote:
> >
> > $ move thisismyimagefor_on.gif thisismyimagefor_off_new.gif
> > $ move thisismyimagefor_off.gif thisismyimagefor_on.gif
> > $ move thisismyimagefor_off_new.gif thisismyimagefor_off.gif
> >
> > [ ... ]
> >
> > I think that this is a problem with 8.3 names and the CVS
> > client not correctly using the right file name. On windows, the
> > long file name is mapped to an 8.3 name, something like:
> > thisis~1.gif for this..._on.gif
> Caching the previous long filename and assigning it to the newly
> created file is _intended_ not regarding the modified content.
> The criterion was "creating a file with the same short filename
> *shortly* after removing a file with the same name". Possible
> resolution derived therefrom: Don't work this fast! :) Have a
> break between single command lines.
>
