Re: The XZ patch?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andreas Ericsson <ae@xxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]