From: John Feuerstein <john@feurix.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.33-rc7
Date: Sun, 07 Feb 2010 11:39:34 +0100 [thread overview]
Message-ID: <4B6E9866.8070108@feurix.com> (raw)
In-Reply-To: <4B6E4AF2.8080603@gmail.com>
I've looked up the GNU tar history, just in case this is relevant:
[1] 1994-11-16 Version 1.11 -z --gzip
[2] 1999-02-01 Version 1.12 -y --bzip2
[3] 2000-10-24 Version 1.12+ -j --bzip2
[4] 2007-10-17 Version 1.20+ --lzma
[5] 2008-06-26 Version 1.20+ -J --lzma
[6] 2008-06-26 Version 1.20+ --lzop
[7] 2009-03-04 Version 1.21+ -J --xz
GNU Tar: http://www.gnu.org/software/tar/
[1] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=17badf1
[2] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=6ccb513
[3] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=caf6047
[4] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=620a136
[5] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=c9a7297
[6] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=c9a7297
[7] http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=c10830a
Linus Torvalds wrote:
> Do people really care about the old-fashioned tar.gz and patch.gz
> files? I've always uploaded the tar-files and patches compressed with
> gzip, because that's the "traditional" way, and then we have a script
> that also re-compresses things as 'bz2' because it compresses better
> and many people are bandwidth-limited and much prefer the better
> compression.
I prefer bzip2 or better, but then again, I'm usually working in GNU
environments.
Mark Lord wrote:
> what about the new lz thing?
> (heck haven't even figured that out yet).
Have a look at:
- http://en.wikipedia.org/wiki/Xz
- http://tukaani.org/xz/format.html
--
John Feuerstein <john@feurix.com>
next prev parent reply other threads:[~2010-02-07 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 22:44 Linux 2.6.33-rc7 Linus Torvalds
2010-02-06 22:49 ` Linus Torvalds
2010-02-06 23:00 ` John Kacur
2010-02-06 23:06 ` Justin P. Mattock
2010-02-07 4:54 ` Mark Lord
2010-02-07 4:58 ` Kyle McMartin
2010-02-07 5:11 ` Mark Lord
2010-02-07 5:09 ` Justin P. Mattock
2010-02-07 10:39 ` John Feuerstein [this message]
2010-02-07 19:10 ` James Cloos
2010-02-08 3:27 ` H. Peter Anvin
2010-02-07 10:20 ` Joel Becker
2010-02-07 10:43 ` Justin P. Mattock
2010-02-07 18:32 ` Linus Torvalds
2010-02-07 18:39 ` Joerg Roedel
2010-02-08 18:28 ` Pavel Machek
2010-02-08 21:49 ` Jiri Slaby
2010-02-10 8:14 ` Pavel Machek
2010-02-08 3:26 ` H. Peter Anvin
2010-02-09 11:30 ` Pádraig Brady
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=4B6E9866.8070108@feurix.com \
--to=john@feurix.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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