From: Jinoh Kang <luke1337@theori.io>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junio@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v4] diff: make diff_free_filespec_data accept NULL
Date: Wed, 11 Nov 2020 12:30:28 +0000 [thread overview]
Message-ID: <01640022-5bda-9712-8228-501374474d5f@theori.io> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2011101638080.18437@tvgsbejvaqbjf.bet>
On 11/10/20 3:38 PM, Johannes Schindelin wrote:
> I had suggested an improvement for this hunk as well as for the test case.
> Fell through the cracks?
You guessed it right. My apologies.
> +test_expect_success 'difftool --cached with unmerged files' '
> + test_when_finished git reset --hard &&
> + echo base >file &&
> + git add file &&
> + git commit -m base &&
>
> This does not advance the committer date. Let's just use the helper
> function we invented to make this much easier:
>
> test_commit base
>
> This has also the advantage of already tagging the outcome.
>
>> + git checkout -B conflict-a &&
>> + git checkout -B conflict-b &&
>> + git checkout conflict-a &&
>> + echo conflict-a >>file &&
>> + git add file &&
>> + git commit -m conflict-a &&
>> + git checkout conflict-b &&
>> + echo conflict-b >>file &&
>> + git add file &&
>> + git commit -m conflict-b &&
>> + git checkout master &&
>> + git merge conflict-a &&
>> + test_must_fail git merge conflict-b &&
>> + : >expect &&
>> + git difftool --cached --no-prompt >actual &&
>> + test_cmp expect actual
>
> Shouldn't this use the `test_must_be_empty` function instead?
>
> How about writing the test case this way:
>
> test_expect_success 'difftool --cached with unmerged files' '
> test_when_finished git reset --hard &&
>
> test_commit conflicting &&
> test_commit conflict-a a conflicting.t &&
> git reset --hard conflicting &&
> test_commit conflict-b b conflicting.t &&
> test_must_fail git merge conflict-a &&
>
> git difftool --cached --no-prompt >out &&
> test_must_be_empty out
> '
The original test code was copied from the "difftool --dir-diff with
unmerged files" case above.
It might be worth cleaning it up too, but let's leave it for another
time.
I'm keeping the return-early code as per Junio's request.
--
Jinoh Kang
Theori
next prev parent reply other threads:[~2020-11-11 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aeb24944-17af-cf53-93f4-e727f9fe9988@theori.io>
[not found] ` <xmqq4km4lppy.fsf@gitster.c.googlers.com>
2020-11-06 17:02 ` [PATCH v2] diff: handle NULL filespecs in run_external_diff Jinoh Kang
2020-11-06 17:14 ` [PATCH v3] diff: make diff_free_filespec_data accept NULL Jinoh Kang
2020-11-10 12:08 ` Johannes Schindelin
2020-11-10 13:16 ` Jinoh Kang
2020-11-10 14:21 ` Jinoh Kang
2020-11-10 17:02 ` Junio C Hamano
2020-11-10 14:06 ` [PATCH v4] " Jinoh Kang
2020-11-10 15:38 ` Johannes Schindelin
2020-11-11 12:30 ` Jinoh Kang [this message]
2020-11-11 16:28 ` Johannes Schindelin
2020-11-10 19:41 ` Junio C Hamano
2020-11-11 12:15 ` [PATCH v5] " Jinoh Kang
2020-11-11 16:27 ` Johannes Schindelin
2020-11-11 19:18 ` Junio C Hamano
2020-11-06 19:18 ` [PATCH v2] diff: handle NULL filespecs in run_external_diff 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=01640022-5bda-9712-8228-501374474d5f@theori.io \
--to=luke1337@theori.io \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junio@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.
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).