From: "Dave Korn" <dave.korn@artimi.com>
To: "'am i the first one to notice'" <cygwin-talk@cygwin.com>
Subject: GNU tar somewhat cleverer than I thought
Date: Sun, 07 Sep 2008 14:14:00 -0000 [thread overview]
Message-ID: <01c901c910f3$e7e239f0$9601a8c0@CAM.ARTIMI.COM> (raw)
http://www.gnu.org/software/tar/manual/tar.html#SEC112
" Note that the file 'cherry' is recorded in the archive under the precise
name 'cherry', not 'food/cherry'. Thus, the archive will contain three files
that all appear to have come from the same directory; if the archive is
extracted with plain 'tar --extract', all three files will be written in the
current directory.
Contrast this with the command,
$ tar -c -f jams.tar grape prune -C food red/cherry
which records the third file in the archive under the name 'red/cherry' so
that, if the archive is extracted using 'tar --extract', the third file will
be written in a subdirectory named 'orange-colored'. "
:) That's some fairly powerful AI they must have there.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next reply other threads:[~2008-09-07 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 14:14 Dave Korn [this message]
2008-09-07 20:33 ` Igor Peshansky
2008-09-07 21:56 ` Dave Korn
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='01c901c910f3$e7e239f0$9601a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@cygwin.com \
/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).