bug-coreutils@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: 61050@debbugs.gnu.org
Subject: bug#61050: mv: add support for --one-file-system
Date: Tue, 24 Jan 2023 20:20:40 -0500	[thread overview]
Message-ID: <Y9CD6ABFEwSfdHjj@vapier> (raw)

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-01-25  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  1:20 Mike Frysinger [this message]
2023-01-25  9:07 ` bug#61050: mv: add support for --one-file-system Paul Eggert
2023-01-25 10:33   ` Pádraig Brady
2023-01-25 13:34   ` Mike Frysinger
2023-01-27 19:13     ` Paul Eggert
2023-01-27 19:50       ` Pádraig Brady

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y9CD6ABFEwSfdHjj@vapier \
    --to=vapier@gentoo.org \
    --cc=61050@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).