From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)
Date: Sat, 19 Dec 2020 09:13:42 -0800 [thread overview]
Message-ID: <xmqqo8ippvll.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPig+cRycw=JnYOxCspJiLWbX10FK_QJhHx3A98oJBSG_MBaoQ@mail.gmail.com> (Eric Sunshine's message of "Sat, 19 Dec 2020 01:44:17 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Sat, Dec 19, 2020 at 12:36 AM Junio C Hamano <gitster@pobox.com> wrote:
>> * ds/maintenance-part-4 (2020-12-09) 6 commits
>> - t7900: make macOS-specific test work on Windows
>> - t7900: fix test failures when invoked individually via --run
>> - maintenance: use Windows scheduled tasks
>> - maintenance: use launchctl on macOS
>> - maintenance: include 'cron' details in docs
>> - maintenance: extract platform-specific scheduling
>>
>> Follow-up on the "maintenance part-3" which introduced scheduled
>> maintenance tasks to support platforms whose native scheduling
>> methods are not 'cron'.
>
> I've read this series in its entirety at each re-roll, and am
> satisfied that the comments from my reviews have been addressed.
> (There may be one or two remaining subjective nits but nothing worth
> holding up the series.)
Thanks.
next prev parent reply other threads:[~2020-12-19 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 5:34 What's cooking in git.git (Dec 2020, #03; Fri, 18) Junio C Hamano
2020-12-19 6:44 ` Eric Sunshine
2020-12-19 17:13 ` Junio C Hamano [this message]
2020-12-19 14:10 ` Felipe Contreras
2020-12-19 17:09 ` Junio C Hamano
2020-12-20 2:19 ` Elijah Newren
2020-12-20 7:32 ` Junio C Hamano
2020-12-21 17:25 ` Elijah Newren
2020-12-21 17:50 ` Junio C Hamano
2020-12-21 12:40 ` Han-Wen Nienhuys
2020-12-21 18:01 ` Junio C Hamano
2020-12-21 19:55 ` [PATCH] SQUASH??? allow t0031 to run with any default branch name Junio C Hamano
2020-12-21 20:19 ` Felipe Contreras
2020-12-22 10:22 ` Han-Wen Nienhuys
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo8ippvll.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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.
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 NNTP newsgroup(s).