From: Junio C Hamano <gitster@pobox.com>
To: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH v2] t3424: new rebase testcase documenting a stat-dirty-like failure
Date: Tue, 18 Feb 2020 13:33:17 -0800 [thread overview]
Message-ID: <xmqqh7znins2.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <pull.712.v2.git.git.1582059331257.gitgitgadget@gmail.com> (Elijah Newren via GitGitGadget's message of "Tue, 18 Feb 2020 20:55:31 +0000")
"Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com> writes:
> t/t3424-rebase-across-mode-change.sh | 48 ++++++++++++++++++++++++++++
t3424 is already taken by en/rebase-backend topic that has been
cooking for some time by now. It seems 342? are all taken and the
next available may be t3433 perhaps (please double check with 'pu')?
next prev parent reply other threads:[~2020-02-18 21:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 17:15 [PATCH] t3424: new rebase testcase documenting a stat-dirty-like failure Elijah Newren via GitGitGadget
2020-02-17 19:12 ` Elijah Newren
2020-02-18 15:05 ` Phillip Wood
2020-02-18 15:59 ` Elijah Newren
2020-02-19 11:01 ` Phillip Wood
2020-02-19 16:00 ` Elijah Newren
2020-02-19 16:38 ` Junio C Hamano
2020-02-19 19:33 ` Phillip Wood
2020-02-18 14:03 ` Johannes Schindelin
2020-02-18 15:55 ` Elijah Newren
2020-02-18 20:55 ` [PATCH v2] " Elijah Newren via GitGitGadget
2020-02-18 21:33 ` Junio C Hamano [this message]
2020-02-18 22:01 ` Elijah Newren
2020-02-18 22:15 ` [PATCH v3] t3433: " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 0/2] " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 1/2] " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 2/2] merge-recursive: fix the refresh logic in update_file_flags Elijah Newren via GitGitGadget
2020-02-19 18:40 ` Junio C Hamano
2020-02-19 19:32 ` Elijah Newren
2020-02-19 21:39 ` 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=xmqqh7znins2.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@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.
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).