Anthony Towns <aj@azure.humbug.org.au> wrote: > tag 274705 + patch > thanks > > So the relevant code seems to be in src/copy.c, where it checks if > "--reply=no" was set _and_ the file isn't overwritable; or if "-i" was > set, or if no option was given and the file isn't overwritable. So > "--reply=no" has an effect when you do: > > touch a b > chmod 000 b > mv --reply=no a b # can't overwrite, so do nothing > > This seems quite deliberate, but afaics it's a bug. I think the attached > patch fixes the problem. > > Cheers, > aj
Thanks for the patch. There's been a lot of talk about mv's --reply option, recently. I'm planning to deprecate that option. Here's the main thread: http://lists.gnu.org/archive/html/bug-coreutils/2005-06/msg00160.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
