From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Derrick Stolee <dstolee@microsoft.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/3] gc: fix handling of crontab magic markers
Date: Tue, 22 Dec 2020 15:22:17 -0800 [thread overview]
Message-ID: <xmqqo8ilfmty.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqsg7xfoj9.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Tue, 22 Dec 2020 14:45:30 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>> +test_expect_success 'stop preserves surrounding schedule' '
>> + echo "Crucial information!" >>cron.txt &&
>> + GIT_TEST_CRONTAB="test-tool crontab cron.txt" git maintenance stop &&
>
> 31345d55 (maintenance: extract platform-specific scheduling,
> 2020-11-24) in ds/maintenance-part-4 needs to adjust this
> exported variable for the tests to pass in 'seen'
>
> Is it just the matter of replacing it with
>
> GIT_TEST_MAINT_SCHEDULER="crontab:test-tool crontab ..."
>
> or is there more to it?
We'll see soon enough; I noticed the above while viewing
https://github.com/git/git/runs/1597371646#step:6:2093
and since then I pushed another round of 'seen' with a non-textual
conflict resolution while merging the ds/maintenance-part-4 topic
in.
next prev parent reply other threads:[~2020-12-22 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 21:26 [PATCH 0/3] gc: fix handling of crontab magic markers Martin Ågren
2020-12-21 21:26 ` [PATCH 1/3] git-maintenance.txt: add missing word Martin Ågren
2020-12-21 21:26 ` [PATCH 2/3] gc: fix handling of crontab magic markers Martin Ågren
2020-12-22 22:45 ` Junio C Hamano
2020-12-22 23:22 ` Junio C Hamano [this message]
2020-12-23 3:50 ` Eric Sunshine
2020-12-23 10:06 ` Martin Ågren
2020-12-23 20:00 ` Junio C Hamano
2020-12-21 21:26 ` [PATCH 3/3] t7900-maintenance: test for " Martin Ågren
2020-12-21 21:54 ` [PATCH 0/3] gc: fix handling of crontab " Derrick Stolee
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=xmqqo8ilfmty.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.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).