From: Junio C Hamano <gitster@pobox.com>
To: Jeff Hostetler <git@jeffhostetler.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2022, #04; Thu, 17)
Date: Wed, 23 Mar 2022 11:28:14 -0700 [thread overview]
Message-ID: <xmqqk0cksev5.fsf@gitster.g> (raw)
In-Reply-To: <eb10fee5-d6ea-b660-e339-d55a4b669c3c@jeffhostetler.com> (Jeff Hostetler's message of "Tue, 22 Mar 2022 14:24:57 -0400")
Jeff Hostetler <git@jeffhostetler.com> writes:
> On 3/17/22 7:34 AM, Junio C Hamano wrote:
>> * jh/builtin-fsmonitor-part-2plus (2022-03-13) 16 commits
>> - fsmonitor-settings: simplify initialization of settings data
>> - fsmonitor--daemon: add _() to calls to error()
>> - fsmonitor--daemon: add _() to calls to die()
>> - compat/fsmonitor/fsm-listen-win32: add _() to calls to error()
>> - compat/fsmonitor/fsm-listen-darwin: add _() to calls to error()
>> - fsmonitor-ipc: add _() to calls to die()
>> - t7527: delete unused verify_status() function
>> - t7527: fix && chaining in matrix_try()
>> - t7527: add parameters to start_daemon to handle args and subshell
>> - t/perf/p7519: cleanup coding style
>> - t/perf/p7519: use grep rather than egrep in test
>> - fsmonitor--daemon: refactor cookie handling for readability
>> - t/helper/fsmonitor-client: cleanup call to parse_options()
>> - compat/fsmonitor/fsm-listen-darwin: split out GCC-specific declarations
>> - update-index: convert advise() messages back to warning()
>> - t/test-lib: avoid using git on LHS of pipe
>> (this branch uses jh/builtin-fsmonitor-part2.)
>> Various small fixes and cleanups on part-2 of the same topic.
>> Needs review.
>> source: <pull.1174.git.1647033303.gitgitgadget@gmail.com>
>
> I have squashed this into part 2 V7, so this series can be
> discarded. Thanks (and sorry for the mess).
Will take a (hopefully final) look, and ...
>> * jh/builtin-fsmonitor-part3 (2022-03-09) 28 commits
>> ...
>> . Merge branch 'jh/builtin-fsmonitor-part2' into jh/builtin-fsmonitor-part3
>> (this branch uses jh/builtin-fsmonitor-part2.)
>> More fsmonitor--daemon.
>> source: <pull.1143.v2.git.1646777727.gitgitgadget@gmail.com>
>
> I just sent a V3 of part 3 that builds upon V7 of part 2.
> The fixups from part 2.5 have been squashed in.
... queue the updated one on top.
Thanks.
next prev parent reply other threads:[~2022-03-23 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 11:34 What's cooking in git.git (Mar 2022, #04; Thu, 17) Junio C Hamano
2022-03-22 1:25 ` Taylor Blau
2022-03-23 18:27 ` Junio C Hamano
2022-03-23 19:20 ` Taylor Blau
2022-03-23 21:37 ` Junio C Hamano
2022-03-23 21:47 ` Taylor Blau
2022-03-22 16:05 ` gc/submodule-update-part2 (was Re: What's cooking in git.git (Mar 2022, #04; Thu, 17)) Glen Choo
2022-03-22 18:24 ` What's cooking in git.git (Mar 2022, #04; Thu, 17) Jeff Hostetler
2022-03-23 18:28 ` Junio C Hamano [this message]
2022-03-23 20:14 ` Jeff Hostetler
-- strict thread matches above, loose matches on Subject: below --
2022-03-19 18:08 Justin Donnelly
2022-03-21 16:51 ` Junio C Hamano
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=xmqqk0cksev5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
/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).