mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "Ævar Arnfjörð Bjarmason" <>
Cc:, "brian m. carlson" <>
Subject: Re: What's cooking in git.git (Apr 2021, #06; Thu, 29)
Date: Sun, 02 May 2021 15:47:51 +0900	[thread overview]
Message-ID: <xmqqeeepbpig.fsf@gitster.g> (raw)
In-Reply-To: <> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 30 Apr 2021 11:34:39 +0200")

Ævar Arnfjörð Bjarmason <> writes:

>> * ab/test-lib-updates (2021-04-29) 11 commits
>>  - test-lib: split up and deprecate test_create_repo()
>>  - test-lib: do not show advice about init.defaultBranch under --verbose
>>  - test-lib: reformat argument list in test_create_repo()
>>  - submodule tests: use symbolic-ref --short to discover branch name
>>  - test-lib functions: add --printf option to test_commit
>>  - describe tests: convert setup to use test_commit
>>  - test-lib functions: add an --annotated option to "test_commit"
>>  - test-lib-functions: document test_commit --no-tag
>>  - test-lib-functions: reword "test_commit --append" docs
>>  - test-lib tests: remove dead GIT_TEST_FRAMEWORK_SELFTEST variable
>>  - test-lib: bring $remove_trash out of retirement
>>  (this branch is used by ab/describe-tests-fix and ab/pickaxe-pcre2.)
>>  Test clean-up.
>>  Waiting for an Ack before merging them to 'next'.
> Is the ack a reply to
> (or here, I
> suppose)?. Sorry about the in-flight hassle.

No, what I meant was that v4 had review comments and v5 was done in
response to that, so I wanted to make sure that reviewers are happy
with the delta between v4 and v5 before taking v5 and declaring it
good just by myself.

  reply	other threads:[~2021-05-02  6:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  9:15 What's cooking in git.git (Apr 2021, #06; Thu, 29) Junio C Hamano
2021-04-30  9:34 ` Ævar Arnfjörð Bjarmason
2021-05-02  6:47   ` Junio C Hamano [this message]
2021-05-06  4:29     ` Junio C Hamano
2021-05-06 15:36       ` Ævar Arnfjörð Bjarmason
2021-05-03  2:38   ` Junio C Hamano
2021-05-02 12:00 ` ZheNing Hu
2021-05-03  1:46   ` Junio C Hamano
2021-05-03 13:35     ` ZheNing Hu

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqeeepbpig.fsf@gitster.g \ \ \ \ \

* 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

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).