git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	Taylor Blau <me@ttaylorr.com>,
	git@vger.kernel.org,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] t5310: stop expecting the default branch name `master`
Date: Tue, 8 Dec 2020 15:00:35 -0500	[thread overview]
Message-ID: <X8/bYzjP569wEL5x@nand.local> (raw)
In-Reply-To: <xmqqim9dbh17.fsf@gitster.c.googlers.com>

On Mon, Dec 07, 2020 at 10:35:48AM -0800, Junio C Hamano wrote:
> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
> >     This one goes on top of tb/pack-bitmap, and requires an update of
> >     js/default-branch-name-tests-final-stretch (it no longer needs to
> >     hard-code GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME in t5310).
>
> As the targetted topic is not in 'next' and marked with "Needs a bit
> of reshuffling?", I'd appreciate this patch to be also forwarded so
> that I do not have to worry about it myself.

Ah, sorry that I missed this before sending out v3. I was hoping that
the fixup would be limited to one patch, but this needs to be either
spread across multiple patches, or applied at the end.

Since I already sent v3, how do you want to handle this?

Thanks,
Taylor

  parent reply	other threads:[~2020-12-08 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 13:17 [PATCH] t5310: stop expecting the default branch name `master` Johannes Schindelin via GitGitGadget
2020-12-07 18:35 ` Junio C Hamano
2020-12-07 18:39   ` Junio C Hamano
2020-12-08 20:00   ` Taylor Blau [this message]
2020-12-08 21:13     ` Junio C Hamano
2020-12-08 21:36       ` Taylor Blau
2020-12-09 14:53         ` 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=X8/bYzjP569wEL5x@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    /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).