git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 0/4]  Adjust t5515 for the upcoming change of the default branch name
Date: Mon, 02 Nov 2020 17:08:32 -0800	[thread overview]
Message-ID: <xmqqlffjp7qn.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.761.git.1604361307.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Mon, 02 Nov 2020 23:55:03 +0000")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> To allow for switching the default of init.defaultBranch to main, we adjust
> the test script t5515 and its friends in t/t5515/. This is a large chunk of
> modifications, but happily, most of them are a totally trivial
> search-and-replace.

Thanks.  I see at the beginning of part #1 the same trick as the
other series is used to protect the under-construction tests.
Nicely done.

Will queue.

      parent reply	other threads:[~2020-11-03  1:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 23:55 [PATCH 0/4] Adjust t5515 for the upcoming change of the default branch name Johannes Schindelin via GitGitGadget
2020-11-02 23:55 ` [PATCH 1/4] t5515: use `main` as the name of the main branch for testing (part 1) Johannes Schindelin via GitGitGadget
2020-11-02 23:55 ` [PATCH 2/4] t5515: use `main` as the name of the main branch for testing (part 2) Johannes Schindelin via GitGitGadget
2020-11-02 23:55 ` [PATCH 3/4] t5515: use `main` as the name of the main branch for testing (part 3) Johannes Schindelin via GitGitGadget
2020-11-02 23:55 ` [PATCH 4/4] t5515: use `main` as the name of the main branch for testing (conclusion) Johannes Schindelin via GitGitGadget
2020-11-03  1:08 ` Junio C Hamano [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=xmqqlffjp7qn.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.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).