From: Jakub Narebski <jnareb@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Mark A Rada <marada@uwaterloo.ca>, git@vger.kernel.org
Subject: Re: The XZ patch?
Date: Wed, 05 Aug 2009 04:12:53 -0700 (PDT) [thread overview]
Message-ID: <m3zlaepl8v.fsf@localhost.localdomain> (raw)
In-Reply-To: <4A795790.9010805@op5.se>
Andreas Ericsson <ae@op5.se> writes:
> Mark A Rada wrote:
> >
> > I was wondering what the fate of my XZ patch was (I didn't do
> > something dumb, did I?). Never got a response after my last
> > submit.
I'm sorry, I didn't reply to the last version, did I? I liked both
patches
> No comments usually meant noone cared enough about the implemented
> feature to comment on it. Personally, I'd never use a compression
> algorithm that hogs as much memory as XZ does. "Good enough" really
> is just that, imo, and bzip2 and gzip are widely available pretty
> much everywhere, whereas I've never heard of XZ before.
Well, there were two patches in last series, and I'd rather liked the
one that decoupled list of _known_ snapshot formats from the list of
snapshot formats projects are _allowed to use_, when project specific
override for 'snapshot' feature is turned on. So for example one can
allow project specific override (so projects can chose whether to have
snapshot, and what formats to use) but for example disable chosing
'tbz' (bzip2 compression) or 'txz' (XZ / LZMA2 compression) formats.
BTW. XZ is just new name (and improved format) for LZMA compression.
Perhaps it should be disabled by default (you can be almost sure for
gzip and bzip2 to be present on platforms one usually deploy gitweb,
but it is not true for xz-utils).
P.S. Snapshot caching.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-08-05 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 1:06 The XZ patch? Mark A Rada
2009-08-05 9:57 ` Andreas Ericsson
2009-08-05 11:12 ` Jakub Narebski [this message]
2009-08-05 18:31 ` Junio C Hamano
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=m3zlaepl8v.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=marada@uwaterloo.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.