{"thread":{"id":"20377","subject":"The XZ patch?","startedAt":"2009-08-05T01:06:24Z","lastAt":"2009-08-05T18:31:31Z","messageCount":4,"participants":["Mark A Rada","Andreas Ericsson","Jakub Narebski","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"119545","messageId":"5F7EF736-9D0B-4455-A0F7-E7314B4F29E4@uwaterloo.ca","threadId":"20377","inReplyTo":null,"subject":"The XZ patch?","fromName":"Mark A Rada","fromEmail":"marada@uwaterloo.ca","sentAt":"2009-08-05T01:06:24Z","receivedAt":"2009-08-05T01:06:24Z","isPatch":false,"sender":{"key":"marada@uwaterloo.ca","avatar":"https://avatars.githubusercontent.com/u/38430?v=4"},"body":"Hi,\n\nI was wondering what the fate of my XZ patch was (I didn't do something\n dumb, did I?). Never got a response after my last submit.\n\n\n\n--\nMark A Rada (ferrous26)\nmarada@uwaterloo.ca\n"},{"id":"119600","messageId":"4A795790.9010805@op5.se","threadId":"20377","inReplyTo":"5F7EF736-9D0B-4455-A0F7-E7314B4F29E4@uwaterloo.ca","subject":"Re: The XZ patch?","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2009-08-05T09:57:36Z","receivedAt":"2009-08-05T09:57:36Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Mark A Rada wrote:\n> Hi,\n> \n> I was wondering what the fate of my XZ patch was (I didn't do something\n> dumb, did I?). Never got a response after my last submit.\n> \n\nNo comments usually meant noone cared enough about the implemented\nfeature to comment on it. Personally, I'd never use a compression\nalgorithm that hogs as much memory as XZ does. \"Good enough\" really\nis just that, imo, and bzip2 and gzip are widely available pretty\nmuch everywhere, whereas I've never heard of XZ before.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n\nConsidering the successes of the wars on alcohol, poverty, drugs and\nterror, I think we should give some serious thought to declaring war\non peace.\n"},{"id":"119606","messageId":"m3zlaepl8v.fsf@localhost.localdomain","threadId":"20377","inReplyTo":"4A795790.9010805@op5.se","subject":"Re: The XZ patch?","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-08-05T11:12:53Z","receivedAt":"2009-08-05T11:12:53Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Andreas Ericsson writes:\n\n> Mark A Rada wrote:\n> >\n> > I was wondering what the fate of my XZ patch was (I didn't do\n> > something dumb, did I?). Never got a response after my last\n> > submit.\n\nI'm sorry, I didn't reply to the last version, did I? I liked both\npatches\n \n> No comments usually meant noone cared enough about the implemented\n> feature to comment on it. Personally, I'd never use a compression\n> algorithm that hogs as much memory as XZ does. \"Good enough\" really\n> is just that, imo, and bzip2 and gzip are widely available pretty\n> much everywhere, whereas I've never heard of XZ before.\n\nWell, there were two patches in last series, and I'd rather liked the\none that decoupled list of _known_ snapshot formats from the list of\nsnapshot formats projects are _allowed to use_, when project specific\noverride for 'snapshot' feature is turned on. So for example one can\nallow project specific override (so projects can chose whether to have\nsnapshot, and what formats to use) but for example disable chosing\n'tbz' (bzip2 compression) or 'txz' (XZ / LZMA2 compression) formats.\n\nBTW. XZ is just new name (and improved format) for LZMA compression.\nPerhaps it should be disabled by default (you can be almost sure for\ngzip and bzip2 to be present on platforms one usually deploy gitweb,\nbut it is not true for xz-utils).\n\nP.S. Snapshot caching.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"119655","messageId":"7vhbwm5czg.fsf@alter.siamese.dyndns.org","threadId":"20377","inReplyTo":"m3zlaepl8v.fsf@localhost.localdomain","subject":"Re: The XZ patch?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-08-05T18:31:31Z","receivedAt":"2009-08-05T18:31:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jakub Narebski writes:\n\n> Andreas Ericsson writes:\n>\n>> Mark A Rada wrote:\n>> >\n>> > I was wondering what the fate of my XZ patch was (I didn't do\n>> > something dumb, did I?). Never got a response after my last\n>> > submit.\n>\n> I'm sorry, I didn't reply to the last version, did I? I liked both\n> patches\n> \n>> No comments usually meant noone cared enough about the implemented\n>> feature to comment on it. Personally, I'd never use a compression\n>> algorithm that hogs as much memory as XZ does. \"Good enough\" really\n>> is just that, imo, and bzip2 and gzip are widely available pretty\n>> much everywhere, whereas I've never heard of XZ before.\n>\n> Well, there were two patches in last series, and I'd rather liked the\n> one that decoupled list of _known_ snapshot formats from the list of\n> snapshot formats projects are _allowed to use_, when project specific\n> override for 'snapshot' feature is turned on. So for example one can\n> allow project specific override (so projects can chose whether to have\n> snapshot, and what formats to use) but for example disable chosing\n> 'tbz' (bzip2 compression) or 'txz' (XZ / LZMA2 compression) formats.\n\nI kind of liked the generic \"disabling\" support, even though I was\nuninterested in adding xz or any other formats. Perhaps it is more useful\nif the patches were in reverse order. First allow site administrators to\nselectively disable the current set of formats, with documentation updates\nfor that feature, then finally add xz.\n"}]}