--- Begin Message ---
|
Subject: |
mv: add support for --one-file-system |
|
Date: |
Tue, 24 Jan 2023 20:20:40 -0500 |
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
Description: PGP signature
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#61050: mv: add support for --one-file-system |
|
Date: |
Fri, 27 Jan 2023 11:13:30 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
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
Description: Text Data
--- End Message ---