GNU bug report logs - #61050
mv: add support for --one-file-system

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#61050: closed (mv: add support for --one-file-system)
Date: Fri, 27 Jan 2023 19:14:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 27 Jan 2023 11:13:30 -0800
with message-id <13ba87b0-ffce-7e57-6c1d-536cafe45754 <at> cs.ucla.edu>
and subject line Re: bug#61050: mv: add support for --one-file-system
has caused the debbugs.gnu.org bug report #61050,
regarding mv: add support for --one-file-system
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
61050: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61050
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mike Frysinger <vapier <at> gentoo.org>
To: bug-coreutils <at> gnu.org
Subject: mv: add support for --one-file-system
Date: Tue, 24 Jan 2023 20:20:40 -0500

[Message part 3 (text/plain, inline)]

mv will automatically use rename, but if that fails (e.g. with EXDEV),
it falls back to copying files.  i'd like to require that the mv be
atomic when relocating a directory, and if it isn't, fallback to other
logic.  to that end, it'd be nice if mv supported --one-file-system and
would return an error when hitting EXDEV rather than copying.
-mike

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: 61050-done <at> debbugs.gnu.org
Subject: Re: bug#61050: mv: add support for --one-file-system
Date: Fri, 27 Jan 2023 11:13:30 -0800

[Message part 6 (text/plain, inline)]

On 2023-01-25 05:34, Mike Frysinger wrote:
> should there be a `--copy` flag to be able to undo `--no-copy` ?

We can add one if there's a need, but mv doesn't have a --clobber option 
to match its --no-clobber and I'm hoping --no-copy is similar.

> personally i always argue against using negative variable names

Yes, I considered calling it "rename_only" instead of "no_copy", but the 
pull of the --no-copy option's name was too strong. Besides, 
"rename_only" wasn't quite right either as "mv --no-copy" does more than 
just renaming (e.g., if the destination is not writeable).

If we can come up with a better name now's a good time to switch. In the 
meantime I installed the attached coreutils patch.

[0001-mv-new-option-no-copy.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.