# The XZ patch? 4 messages from 2009-08-05 to 2009-08-05. Participants: Mark A Rada, Andreas Ericsson, Jakub Narebski, Junio C Hamano. Thread: https://gitlist.dev/t/20377 ## Mark A Rada, 2009-08-05 01:06 Subject: The XZ patch? Message-ID: <5F7EF736-9D0B-4455-A0F7-E7314B4F29E4@uwaterloo.ca> URL: https://gitlist.dev/e/5F7EF736-9D0B-4455-A0F7-E7314B4F29E4%40uwaterloo.ca ``` Hi, 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. -- Mark A Rada (ferrous26) marada@uwaterloo.ca ``` ## Andreas Ericsson, 2009-08-05 09:57 Subject: Re: The XZ patch? Message-ID: <4A795790.9010805@op5.se> URL: https://gitlist.dev/e/4A795790.9010805%40op5.se In-Reply-To: <5F7EF736-9D0B-4455-A0F7-E7314B4F29E4@uwaterloo.ca> ``` Mark A Rada wrote: > Hi, > > 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. > 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. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ``` ## Jakub Narebski, 2009-08-05 11:12 Subject: Re: The XZ patch? Message-ID: URL: https://gitlist.dev/e/m3zlaepl8v.fsf%40localhost.localdomain In-Reply-To: <4A795790.9010805@op5.se> ``` Andreas Ericsson 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 ``` ## Junio C Hamano, 2009-08-05 18:31 Subject: Re: The XZ patch? Message-ID: <7vhbwm5czg.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vhbwm5czg.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Jakub Narebski writes: > Andreas Ericsson 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. I kind of liked the generic "disabling" support, even though I was uninterested in adding xz or any other formats. Perhaps it is more useful if the patches were in reverse order. First allow site administrators to selectively disable the current set of formats, with documentation updates for that feature, then finally add xz. ```