Re: [PATCH v2 00/20] Separate `ref_cache` into a separate module
- From
Ramsay Jones <ramsay@ramsayjones.plus.com>
- Date
- Apr 1, 2017, 21:26 UTC
- Message-ID
- <9b9a6cc2-a7d4-a7b8-0483-5aefdf926ca7@ramsayjones.plus.com>
- In-Reply-To
- <xmqq1std1lmb.fsf@gitster.mtv.corp.google.com>
On 31/03/17 17:01, Junio C Hamano wrote:
Show 22 quoted lines
> Michael Haggerty <mhagger@alum.mit.edu> writes: > >> This version literally only contains a few commit message changes and >> one minor comment changes relative to v1. The code is identical. I >> wasn't sure whether it is even worth sending this patch series to the >> ML again; Junio, if you'd prefer I just send a link to a published >> branch in such cases, please let me know. > > The review on the list is not about letting me pick it up, but is > about giving reviewing contributors a chance to comment. I think > for a series this important ;-) it is good that you are giving it > multiple exposures so that people who were offline the last time can > have a chance to look at it, even if the update is minimum. > >> This patch series is also available from my GitHub fork [2] as branch >> "separate-ref-cache". These patches depend on Duy's >> nd/files-backend-git-dir branch. > > I am getting the impression that the files-backend thing as well as > this topic are ready for 'next'. Please stop me if I missed something > in these topics (especially the other one) that needs updating > before that happens.
Hmm, are these branches 'tangled' with nd/prune-in-worktree? (I think they were at one point, but maybe not now?).
I sent Duy some comments on that branch (an unused function and a 'plain integer used as NULL pointer' warning).
ATB, Ramsay Jones