[PATCH 06 of 11] internals: document compression negotiation

[Augie Fackler]

> On Nov 21, 2016, at 7:00 PM, Kyle Lippincott <spectral at pewpew.net> wrote:
> 
> The 2 character limitation concerns me, because it doesn't give many usable values (considering that a lot of compression has a Z in it, this is perhaps fewer than you might expect) or mechanisms to describe variations.
> 
> Examples:
> Would lz4 be encoded as z4, l4, or lz?  (lz seems bad, since lzma, lzf, lzo, quicklz)
> Would lz4-without-framing (currently in use by remotefilelog) be represented differently than lz4-with-framing?  How so?

I thought about suggesting what my old Mac brain would call a fourcc instead of a two character code. I’m +0 on the idea of at least using four characters.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20161121/8d86679d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20161121/8d86679d/attachment.sig>