[PATCH 3 of 8 V2] internals: document compression negotiation

Gregory Szorc gregory.szorc at gmail.com
Sat Dec 24 13:50:13 EST 2016


On Sat, Dec 24, 2016 at 11:47 AM, Augie Fackler <raf at durin42.com> wrote:

>
> On Dec 24, 2016, at 1:34 PM, Gregory Szorc <gregory.szorc at gmail.com>
> wrote:
>
> Where do we stand with this series? I was waiting for feedback, but none
> arrived.
>
>
> I believe I had asked that others look at it, and hearing nothing, we
> should conclude nobody else cares and move on and queue it with whatever
> little bits I had to say on this v2. Does that work for you?
>
> (I did give you feedback, right?)
>
> I'd like to get zstd into the wire protocol and revlogs for 4.1, otherwise
> it isn't very useful (I've been holding off patchbombing the revlog series
> because I already have enough things in flight). With the holidays, we
> effectively have 2 weeks before freeze.
>
>
> Agreed.
>
>
> FWIW, getting reviews this cycle has been extremely frustrating to me. I
> was planning on landing zstd, `hg debugupgraderepo`, `hg display`, and
> various polish work for more robust zstd integration in the 4.1 release.
> It's now looking like a good chunk of that work won't make it. The most
> frustrating part is that most of the code was ready in November :/ I think
> there needs to be a discussion about scaling code review (no later than the
> next sprint) because it's been obvious for a few months now that things
> aren't as well-oiled as they were several months ago.
>
>
> Also agreed. Note that this one got lost while you were on vacation (or
> something?), and debugupgraderepo I left for marmoute at his explicit
> request, but I haven’t seen movement there.
>

Yeah, I did take a bit of a pause on this series because a) I was waiting
for feedback b) I had a week long business trip c) I took a mini vacation
the week after.

But since silence is consent on this series, I'll resume steaming ahead.
Thanks for the clarification.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20161224/37abde71/attachment.html>


More information about the Mercurial-devel mailing list