git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Victoria Dye <vdye@github.com>
Cc: git@vger.kernel.org
Subject: Re: vd/*
Date: Thu, 18 Aug 2022 12:09:04 -0700	[thread overview]
Message-ID: <xmqq5yippdwv.fsf@gitster.g> (raw)
In-Reply-To: <491d822c-56f0-71df-8815-91ab863ebc9d@github.com> (Victoria Dye's message of "Thu, 18 Aug 2022 11:12:00 -0700")

Victoria Dye <vdye@github.com> writes:

> 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.

  reply	other threads:[~2022-08-18 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  2:23 What's cooking in git.git (Aug 2022, #06; Wed, 17) Junio C Hamano
2022-08-18 12:42 ` js/bisect-in-c (was: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Ævar Arnfjörð Bjarmason
2022-08-19 11:06   ` Johannes Schindelin
2022-08-19 14:28     ` Ævar Arnfjörð Bjarmason
2022-08-18 13:18 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Derrick Stolee
2022-08-18 13:19   ` Derrick Stolee
2022-08-18 15:00 ` ds/* (was Re: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Derrick Stolee
2022-08-18 17:39   ` Junio C Hamano
2022-08-18 18:12 ` vd/* (was: " Victoria Dye
2022-08-18 19:09   ` Junio C Hamano [this message]
2022-08-18 22:42 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Jonathan Tan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5yippdwv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=vdye@github.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).