From: Antonin Delpeuch <antonin@delpeuch.eu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] merge-ll: expose revision names to custom drivers
Date: Thu, 18 Jan 2024 21:56:01 +0100 [thread overview]
Message-ID: <00fd20e2-73f5-42ca-b9a8-1ee227150eff@delpeuch.eu> (raw)
In-Reply-To: <xmqq1qaeqtw7.fsf@gitster.g>
Hi Junio,
Thanks a lot for your review! (and many apologies for the double sending
as HTML…)
On 18/01/2024 21:16, Junio C Hamano wrote:
> Or you could fix %O's description "while at it" and use the right
> term from the get-go for %S.
Agreed, I'll do that, it also feels more fitting to me.
> I see some funny indentation for "S" here.
Oops, sorry about that.
>> @@ -173,7 +179,7 @@ test_expect_success !WINDOWS 'custom merge driver that is killed with a signal'
>>
>> git reset --hard anchor &&
>> git config --replace-all \
>> - merge.custom.driver "./custom-merge %O %A %B 0 %P" &&
>> + merge.custom.driver "./custom-merge %O %A %B 0 %P %S %X %Y" &&
>> git config --replace-all \
>> merge.custom.name "custom merge driver for testing" &&
> ;-)
>
> This one is expected to die and not produce meaningful output;
> I was wondering why this does not need to make corresponding changes
> to the expected output pattern like the earlier tests.
As far as I can tell, this test does not compare the result of the merge
to the expected merge driver output, because that output is expected to
be disregarded by git given that the merge driver died (see the last two
lines). So it seems normal to me that we don't need to adapt the
expected output: the repository files are still left unchanged.
I'll submit a new version of the patch with the two changes above.
Antonin
next prev parent reply other threads:[~2024-01-18 21:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 14:26 [PATCH] merge-ll: expose revision names to custom drivers Antonin Delpeuch via GitGitGadget
2024-01-18 15:25 ` Kristoffer Haugsbakk
2024-01-18 15:42 ` Antonin Delpeuch
2024-01-18 15:43 ` [PATCH v2] " Antonin Delpeuch via GitGitGadget
2024-01-18 20:16 ` Junio C Hamano
2024-01-18 20:56 ` Antonin Delpeuch [this message]
2024-01-18 22:09 ` [PATCH v3] " Antonin Delpeuch via GitGitGadget
2024-01-19 20:02 ` Antonin Delpeuch
2024-01-20 17:25 ` Junio C Hamano
2024-01-20 14:13 ` Phillip Wood
2024-01-20 17:37 ` Junio C Hamano
2024-01-20 18:23 ` Phillip Wood
2024-01-20 22:49 ` Junio C Hamano
2024-01-24 20:09 ` [PATCH v4] " Antonin Delpeuch via GitGitGadget
2024-01-24 21:17 ` 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=00fd20e2-73f5-42ca-b9a8-1ee227150eff@delpeuch.eu \
--to=antonin@delpeuch.eu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).