vd/* (was: Re: What's cooking in git.git (Aug 2022, #06; Wed, 17))

From: Victoria Dye <vdye@github.com>
Date: Aug 18, 2022, 18:12 UTC
Message-ID: <491d822c-56f0-71df-8815-91ab863ebc9d@github.com>
In-Reply-To: <xmqq7d36s31e.fsf@gitster.g>

Junio C Hamano wrote:

Show 12 quoted lines

> * vd/scalar-enables-fsmonitor (2022-08-16) 5 commits
>  - scalar: update technical doc roadmap with FSMonitor support
>  - scalar unregister: stop FSMonitor daemon
>  - scalar: enable built-in FSMonitor on `register`
>  - scalar-[un]register: clearly indicate source of error
>  - scalar-unregister: handle error codes greater than 0
> 
>  "scalar" now enables built-in fsmonitor on enlisted repositories,
>  when able.
> 
>  Will merge to 'next'?
>  source: <pull.1324.v2.git.1660694290.gitgitgadget@gmail.com>

This should probably be "Expecting a reroll."; I have a couple of changes to make in response to [1] and [2] and will send the new version later today.

[1] https://lore.kernel.org/git/f5388e4d-7eb7-9333-6a8e-86ce449aced0@github.com/ [2] https://lore.kernel.org/git/82716e5b-3522-68f5-7479-1b39811e0cb2@github.com/

Show 19 quoted lines

> * vd/scalar-generalize-diagnose (2022-08-12) 11 commits
>  - scalar: update technical doc roadmap
>  - scalar-diagnose: use 'git diagnose --mode=all'
>  - builtin/bugreport.c: create '--diagnose' option
>  - builtin/diagnose.c: add '--mode' option
>  - builtin/diagnose.c: create 'git diagnose' builtin
>  - diagnose.c: add option to configure archive contents
>  - scalar-diagnose: move functionality to common location
>  - scalar-diagnose: move 'get_disk_info()' to 'compat/'
>  - scalar-diagnose: add directory to archiver more gently
>  - scalar-diagnose: avoid 32-bit overflow of size_t
>  - scalar-diagnose: use "$GIT_UNZIP" in test
> 
>  The "diagnose" feature to create a zip archive for diagnostic
>  material has been lifted from "scalar" and made into a feature of
>  "git bugreport".
> 
>  Will merge to 'next'?
>  source: <pull.1310.v4.git.1660335019.gitgitgadget@gmail.com>

I think the review on this has stabilized (and, personally, I'm happy with the current version). Assuming no late-stage reviews come in, I think this is ready for 'next'.