From: Titus von Boxberg <titus@v9g.de>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH 1 of 1] scripts/functions: extract: portable call for old and defective tars
Date: Tue, 22 Nov 2011 18:08:00 -0000 [thread overview]
Message-ID: <34880CEA-E3E0-4F06-9071-35F9A051B8D5@v9g.de> (raw)
In-Reply-To: <201111221809.44609.yann.morin.1998@anciens.enib.fr>
Am 22.11.2011 um 18:09 schrieb Yann E. MORIN:
> Titus, All,
>
> On Tuesday 22 November 2011 10:30:23 Titus von Boxberg wrote:
>> # HG changeset patch
>> # User Titus von Boxberg <titus@v9g.de>
>> # Date 1321952890 -3600
>> # Node ID ac30f53965908a4341a5cf21ba67d707a8f0d68e
>> # Parent 3c1a3fc051cb46d1bad9cbe2a601c5c4aa48876c
>> scripts/functions: extract: portable call for old and defective tars
>
> Why not use:
> xz : xzcat
> lzma : lzcat
> bzip2 : bzcat
> gzip : zcat
>
> I believe that, if a specific compressor is available, the corresponding
> 'cat' counterpart is also available. At least, that has been my experience
> with all the "standard" distro I've used.
Yann,
you gave the reason yourself:
That <compressor>cat would always be available is just belief.
The availability of <compressor -dc> is granted by definition.
Regards
Titus
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-22 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 9:34 [PATCH 0 of 1] reworked: using tar with xz and lzma archives Titus von Boxberg
2011-11-22 9:34 ` [PATCH 1 of 1] scripts/functions: extract: portable call for old and defective tars Titus von Boxberg
2011-11-22 17:10 ` Yann E. MORIN
2011-11-22 18:08 ` Titus von Boxberg [this message]
2011-11-25 22:50 ` Yann E. MORIN
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=34880CEA-E3E0-4F06-9071-35F9A051B8D5@v9g.de \
--to=titus@v9g.de \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).