git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: vd/*

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 18, 2022, 19:09 UTC
Message-ID
<xmqq5yippdwv.fsf@gitster.g>
In-Reply-To
<491d822c-56f0-71df-8815-91ab863ebc9d@github.com>
Victoria Dye <vdye@github.com> writes:
Show 43 quoted lines
> Junio C Hamano wrote:
>> * 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/
>
>> * 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'.
Thanks.
Previous: Victoria DyeNext: Jonathan Tan
Message 10 of 11 in “What's cooking in git.git (Aug 2022, #06; Wed, 17)”
  1. Junio C HamanoAug 18, 2022
  2. js/bisect-in-c (was: What's cooking in git.git (Aug 2022, #06; Wed, 17))Ævar Arnfjörð Bjarmason, Aug 18, 2022
  3. Johannes SchindelinAug 19, 2022
  4. Ævar Arnfjörð BjarmasonAug 19, 2022
  5. Derrick StoleeAug 18, 2022
  6. Derrick StoleeAug 18, 2022
  7. ds/* (was Re: What's cooking in git.git (Aug 2022, #06; Wed, 17))Derrick Stolee, Aug 18, 2022
  8. Junio C HamanoAug 18, 2022
  9. vd/* (was: Re: What's cooking in git.git (Aug 2022, #06; Wed, 17))Victoria Dye, Aug 18, 2022
  10. Junio C HamanoAug 18, 2022
  11. Jonathan TanAug 18, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.