All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/3] t2106 vs. the default branch name
Date: Wed, 18 Nov 2020 21:56:41 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2011182152580.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqq1rgq1jgf.fsf@gitster.c.googlers.com>

Hi Junio,

On Wed, 18 Nov 2020, Junio C Hamano wrote:

> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
> > Yet another thing I noticed while working on
> > https://github.com/gitgitgadget/git/pull/762.
> >
> > Johannes Schindelin (3):
> >   t2106: adjust style to the current conventions
> >   t2106: make test independent of the current main branch name
> >   t2106: ensure that the checkout fails for the expected reason
> >
> >  t/t2106-update-index-assume-unchanged.sh | 31 +++++++++++++-----------
> >  1 file changed, 17 insertions(+), 14 deletions(-)
>
> This seems to partly replicate and partly deprecate what is in that
> final stretch 27-or-28 patch series does to the same test script.
> Are we taking this and then removing a patch or two from that larger
> series?

Sorry, I meant to explain my current thinking: for v3, I want to
accommodate your wish (to mark every test script with the hard-coded
default branch name individually, and only those test scripts that
actually need to hard-code it). It is not only to fulfill your wish, I got
genuinely curious what would actually be needed to make that happen.

The four test scripts for which I sent patch series in the past hours to
remove the use of the name `master` won't be touched by v3 of this here
patch series at all (because it won't be necessary anymore).

Ciao,
Dscho

  reply	other threads:[~2020-11-18 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 14:49 [PATCH 0/3] t2106 vs. the default branch name Johannes Schindelin via GitGitGadget
2020-11-18 14:49 ` [PATCH 1/3] t2106: adjust style to the current conventions Johannes Schindelin via GitGitGadget
2020-11-18 14:49 ` [PATCH 2/3] t2106: make test independent of the current main branch name Johannes Schindelin via GitGitGadget
2020-11-18 18:26   ` Junio C Hamano
2020-11-18 14:49 ` [PATCH 3/3] t2106: ensure that the checkout fails for the expected reason Johannes Schindelin via GitGitGadget
2020-11-18 20:46 ` [PATCH 0/3] t2106 vs. the default branch name Junio C Hamano
2020-11-18 20:56   ` Johannes Schindelin [this message]
2020-11-18 21:53     ` Junio C Hamano
2020-11-18 22:25       ` 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=nycvar.QRO.7.76.6.2011182152580.56@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.