From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jan.kratochvil@redhat.com, jim@meyering.net, gdb@sourceware.org
Subject: Re: xz-compressed release tarballs?
Date: Fri, 27 Jan 2012 09:36:00 -0000 [thread overview]
Message-ID: <83hazhzdzb.fsf@gnu.org> (raw)
In-Reply-To: <20120127050151.GL31397@adacore.com>
> Date: Fri, 27 Jan 2012 09:01:51 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, jim@meyering.net, gdb@sourceware.org
>
> I think we can make everyone happy by simply adding the .xz format,
> giving us 3 release tarballs. That would cost about 25-30MB extra
> times 2-3 releases a year. I am not opposed to getting rid of the
> .bz2 format, however.
Fine with me, although I don't really understand what's problem, as
disk space is no longer at a premium and neither is network bandwidth
(certainly not for those who lobby for .xz). Sometimes it looks to me
like people are simply pushing to use newer tools just because they
shine brighter.
next prev parent reply other threads:[~2012-01-27 9:36 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 [this message]
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
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=83hazhzdzb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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