git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] t5310: stop expecting the default branch name `master`
Date: Wed, 9 Dec 2020 15:53:40 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2012091553210.25979@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <X8/x5LaeZgbvXT0l@nand.local>

Hi Taylor,

On Tue, 8 Dec 2020, Taylor Blau wrote:

> On Tue, Dec 08, 2020 at 01:13:35PM -0800, Junio C Hamano wrote:
> > Taylor Blau <me@ttaylorr.com> writes:
> >
> > > 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?
> >
> > As I have many other topics on the table to attend to, I can skip v3
> > and take v4 if it is not too much trouble to fix the issue at the
> > source.  Thanks.
>
> No problem at all. Your instructions were spot on (4/24 and 15/24 needed
> adjusting, as well as the later patches which could no longer be
> applied after modifying those two).
>
> Checking my work against upstream, I can see that the only diff lines
> which mention "master" are removals:
>
> $ git diff @{u}.. | grep master
> -	git checkout master &&
> -	bitmaptip=$(git rev-parse master) &&
> -		git rev-list --count other...master >expect &&
> -		git rev-list --use-bitmap-index --count other...master >actual &&
> -	git --git-dir=clone.git fetch origin master:master &&
> -	git --git-dir=clone.git fetch origin master:master &&
>
> and spot checking the inter-diff between what I have and what Johannes
> posted I can see that they are the same. I've added some Helped-by lines
> in the relevant patches to indicate where the suggestions came from.
>
> v4 coming shortly...

Thank you so much for picking this up!

Ciao,
Dscho

      reply	other threads:[~2020-12-09 14:55 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
2020-12-08 21:13     ` Junio C Hamano
2020-12-08 21:36       ` Taylor Blau
2020-12-09 14:53         ` Johannes Schindelin [this message]

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=nycvar.QRO.7.76.6.2012091553210.25979@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.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).