From: rgl@antares-labs.eu
To: 9front@9front.org
Subject: tar(1): document -T misbehavior
Date: Sun, 3 Nov 2019 23:21:56 +0100 [thread overview]
Message-ID: <62506C8CDFCEBC0C5E9B89938844A160@antares-labs.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 164 bytes --]
hi there,
since we couldn't come up with a reasonable
solution to T's mistreatment of directories,
we should at least inform the user about it
to avoid surprises.
[-- Attachment #2: Type: text/plain, Size: 322 bytes --]
diff -r fe7fc19b1e64 sys/man/1/tar
--- a/sys/man/1/tar Sun Nov 03 15:20:57 2019 +0100
+++ b/sys/man/1/tar Sun Nov 03 23:13:38 2019 +0100
@@ -195,6 +195,10 @@
key (append)
cannot be used on compressed archives.
.PP
+The
+.B T
+key (write metadata) won't work for non-empty directories.
+.PP
.IR Tar ,
thus
.IR dircp ,
reply other threads:[~2019-11-03 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62506C8CDFCEBC0C5E9B89938844A160@antares-labs.eu \
--to=rgl@antares-labs.eu \
--cc=9front@9front.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 NNTP newsgroup(s).