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
>
> When I move it, the 8.3 name stays the same. So, when I swap
> the file names, their 8.3 names stay the same but the long file
> names are different.
>
> If I copy the file to temporary file names, generating a new
> 8.3, everything works.
>
> Anyone have these problems before? Is this a windows cvs client
> bug?
In MS' opinion it's a feature. AFAIK this mechanism was meant
for the non Windows programs like DOS editors to get access to
long filenamed files without destroying their long names.
Consider the following scenario: Saving an editor file is
usually done in a few steps
- moving the original file out of the way (maybe to .bak)
- writing the modified content under the original name
- maybe removing the moved away original
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.
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED]
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
