From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Michael V. Scovetta" <michael.scovetta@gmail.com>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>,
git@vger.kernel.org
Subject: Re: [PATCH] sequencer: detect author name errors in read_author_script()
Date: Mon, 03 Oct 2022 11:05:05 -0700 [thread overview]
Message-ID: <xmqq7d1gu6jy.fsf@gitster.g> (raw)
In-Reply-To: <YzseUy8bRT0LN2Wp@coredump.intra.peff.net> (Jeff King's message of "Mon, 3 Oct 2022 13:39:31 -0400")
Jeff King <peff@peff.net> writes:
> On Mon, Oct 03, 2022 at 01:27:37PM -0400, Jeff King wrote:
>
>> -check_broken_author 'unknown key in author-script' '
>> +test_expect_success 'unknown key in author-script' '
>> + create_conflict &&
>> +
>> echo "GIT_AUTHOR_BOGUS=${SQ}whatever${SQ}" \
>> - >>.git/rebase-merge/author-script'
>> + >>.git/rebase-merge/author-script &&
>>
>> + check_resolve_fails
>> +'
>>
>> test_done
>>
>> That makes the boilerplate shorter in the "-v" output but focuses on the
>> actual modification that breaks the author-script.
>
> Note that we do still keep the ${SQ} bits here. They're necessary for
> the same reason: before and after a snippet is being passed through a
> variable. Whereas in yours we'd use stdin. I _do_ like that approach in
> general, but it is unlike the rest of the test suite. Maybe it's worth
> resurrecting:
>
> https://lore.kernel.org/git/YHDUg6ZR5vu93kGm@coredump.intra.peff.net/
>
> ?
Yeah, it is indeed quite tempting.
next prev parent reply other threads:[~2022-10-03 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 6:39 Bug Report: Duplicate condition in read_author_script (sequencer.c) Michael V. Scovetta
2022-10-03 8:45 ` [PATCH] sequencer: detect author name errors in read_author_script() Jeff King
2022-10-03 9:29 ` Phillip Wood
2022-10-03 17:15 ` Jeff King
2022-10-03 9:40 ` Ævar Arnfjörð Bjarmason
2022-10-03 17:27 ` Jeff King
2022-10-03 17:39 ` Jeff King
2022-10-03 18:05 ` Junio C Hamano [this message]
2022-10-03 16:34 ` Junio C Hamano
2022-10-03 17:35 ` Jeff King
2022-10-03 18:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7d1gu6jy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=michael.scovetta@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.