Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: The XZ patch? · Junio C Hamano <hidden> · 2016-06-15

Re: The XZ patch?

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:09

Jakub Narebski [off-list ref] writes:
Andreas Ericsson [off-list ref] writes:
quoted
Mark A Rada wrote:
quoted
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
 
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help