From: Ondrej Valousek <ondrej.valousek.xm@renesas.com>
To: 61035@debbugs.gnu.org
Cc: Ondrej Valousek <ondrej.valousek.xm@renesas.com>
Subject: bug#61035: [PATCH] cp: improve help regarding ACLs
Date: Tue, 24 Jan 2023 09:42:30 +0100 [thread overview]
Message-ID: <20230124084229.1923075-1-ondrej.valousek.xm@renesas.com> (raw)
Improve help to clarify ACL handling
---
src/cp.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/cp.c b/src/cp.c
index 016ae8988..73ffd34e9 100644
--- a/src/cp.c
+++ b/src/cp.c
@@ -239,6 +239,11 @@ When --reflink[=always] is specified, perform a lightweight copy, where the\n\
data blocks are copied only when modified. If this is not possible the copy\n\
fails, or if --reflink=auto is specified, fall back to a standard copy.\n\
Use --reflink=never to ensure a standard copy is performed.\n\
+"), stdout);
+ fputs (_("\
+\n\
+--preserve=mode also copies ACLs but only if the destination filesystem\n\
+supports ACLs of the same type (i.e. no Posix <> NFSv4 ACLs conversion)\n\
"), stdout);
emit_backup_suffix_note ();
fputs (_("\
--
2.39.0
next reply other threads:[~2023-01-24 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 8:42 Ondrej Valousek [this message]
2023-01-24 23:23 ` bug#61035: [PATCH] cp: improve help regarding ACLs Paul Eggert
2023-01-25 8:26 ` Ondrej Valousek
2023-01-25 9:11 ` Paul Eggert
2023-01-25 9:24 ` Ondrej Valousek
2023-01-25 20:42 ` Paul Eggert
2023-01-25 21:56 ` Ondrej Valousek
2023-01-25 22:01 ` Paul Eggert
2023-01-29 11:06 ` Kamil Dudka
2023-01-29 22:04 ` Paul Eggert
2023-01-30 7:40 ` Kamil Dudka
2023-01-30 8:19 ` Ondrej Valousek
2023-01-31 18:46 ` Paul Eggert
2023-01-31 21:23 ` Ondrej Valousek
2023-01-31 21:56 ` Paul Eggert
2023-02-01 7:30 ` Kamil Dudka
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=20230124084229.1923075-1-ondrej.valousek.xm@renesas.com \
--to=ondrej.valousek.xm@renesas.com \
--cc=61035@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).