From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
jim@meyering.net, gdb@sourceware.org
Subject: Re: xz-compressed release tarballs?
Date: Fri, 27 Jan 2012 02:37:00 -0000 [thread overview]
Message-ID: <4F220D22.6010501@rtems.org> (raw)
In-Reply-To: <83vcnyyww0.fsf@gnu.org>
On 01/26/2012 10:30 PM, Eli Zaretskii wrote:
>> Date: Thu, 26 Jan 2012 21:31:48 +0100
>> From: Jan Kratochvil<jan.kratochvil@redhat.com>
>> Cc: gdb@sourceware.org
>>
>> On Thu, 26 Jan 2012 21:21:47 +0100, Jim Meyering wrote:
>>> With xz -9e, that would have been 25% smaller,
>>> at 15282412 bytes (contrast w/20614020 for .bz2).
+1
>> Previous proposal by me:
>> xz for the new release tip
>> http://sourceware.org/ml/gdb/2009-09/msg00341.html
>
> Please think a little about those who don't necessarily have a tar
> that knows about xz. The world doesn't end with GNU/Linux.
These days, even FreeBSD is shipping their OS tar.xz (rsp. txz) packaged:
c.f. ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/9.0-RELEASE/
Ralf
next prev parent reply other threads:[~2012-01-27 2:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 20:22 Jim Meyering
2012-01-26 20:32 ` Jan Kratochvil
2012-01-26 21:31 ` Eli Zaretskii
2012-01-26 22:15 ` Jan Kratochvil
2012-01-26 23:10 ` Samuel Bronson
2012-01-27 1:49 ` Mike Frysinger
2012-01-27 9:13 ` Eli Zaretskii
2012-01-27 5:02 ` Joel Brobecker
2012-01-27 9:36 ` Eli Zaretskii
2012-01-30 19:08 ` Tom Tromey
2012-01-27 1:48 ` Mike Frysinger
2012-01-27 9:12 ` Eli Zaretskii
2012-01-27 18:41 ` Mike Frysinger
2012-01-28 8:21 ` Eli Zaretskii
2012-01-28 23:08 ` Mike Frysinger
2012-01-29 3:55 ` Eli Zaretskii
2012-01-30 6:26 ` Mike Frysinger
2012-01-30 17:49 ` Alfred M. Szmidt
2012-01-30 19:54 ` Stan Shebs
2012-01-30 20:53 ` Pedro Alves
2012-01-30 21:06 ` Mike Frysinger
2012-01-27 2:37 ` Ralf Corsepius [this message]
2012-01-27 9:26 ` Jan Kratochvil
2012-01-27 20:27 ` Mike Frysinger
2012-01-27 20:30 ` Marek Polacek
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=4F220D22.6010501@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jim@meyering.net \
/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