From: Junio C Hamano <gitster@pobox.com>
To: "Eric Sunshine via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH 0/3] fix failing t4301 test and &&-chain breakage
Date: Sun, 28 Aug 2022 13:05:46 -0700 [thread overview]
Message-ID: <xmqq35dgt9ph.fsf@gitster.g> (raw)
In-Reply-To: <pull.1339.git.1661663879.gitgitgadget@gmail.com> (Eric Sunshine via GitGitGadget's message of "Sun, 28 Aug 2022 05:17:56 +0000")
"Eric Sunshine via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Eric Sunshine (3):
> t4301: account for behavior differences between sed implementations
> t4031: fix broken &&-chains and add missing loop termination
> t4301: emit blank line in more idiomatic fashion
>
> t/t4301-merge-tree-write-tree.sh | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
The second one is off by 270.
next prev parent reply other threads:[~2022-08-28 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 5:17 [PATCH 0/3] fix failing t4301 test and &&-chain breakage Eric Sunshine via GitGitGadget
2022-08-28 5:17 ` [PATCH 1/3] t4301: account for behavior differences between sed implementations Eric Sunshine via GitGitGadget
2022-08-28 5:17 ` [PATCH 2/3] t4031: fix broken &&-chains and add missing loop termination Eric Sunshine via GitGitGadget
2022-08-28 5:17 ` [PATCH 3/3] t4301: emit blank line in more idiomatic fashion Eric Sunshine via GitGitGadget
2022-08-28 20:05 ` Junio C Hamano [this message]
2022-08-28 20:46 ` [PATCH 0/3] fix failing t4301 test and &&-chain breakage Eric Sunshine
2022-08-29 5:36 ` Junio C Hamano
2022-08-30 2:53 ` Elijah Newren
2022-08-30 2:56 ` Eric Sunshine
2022-08-30 2:59 ` Elijah Newren
2022-08-30 2:52 ` Elijah Newren
2022-08-30 14:02 ` Johannes Schindelin
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=xmqq35dgt9ph.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@gmail.com \
--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).