git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: ab/c99 + ab/hook-tests (was: What's cooking in git.git (Feb 2022, #06; Wed, 23))
Date: Thu, 24 Feb 2022 10:11:01 +0100	[thread overview]
Message-ID: <220224.86fso8aao1.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq1qztortk.fsf@gitster.g>


On Wed, Feb 23 2022, Junio C Hamano wrote:

Replying to these together, since they're rather trivial:

> * ab/c99 (2022-02-21) 2 commits
>  - C99: remove hardcoded-out !HAVE_VARIADIC_MACROS code
>  - git-compat-util.h: clarify GCC v.s. C99-specific in comment
>
>  source: <cover-v4-0.2-00000000000-20220221T160440Z-avarab@gmail.com>

I think all comments/concerns have been addressed here (thanks to your
reviews), and this should be ready to merge down.

> * ab/hook-tests (2022-02-19) 2 commits
>  - hook tests: use a modern style for "pre-push" tests
>  - hook tests: test for exact "pre-push" hook input
>
>  source: <cover-0.2-00000000000-20220218T204719Z-avarab@gmail.com>

Taylor acked this rather trivial series:
https://lore.kernel.org/git/YhBvBscyDAfndvSB@nand.local/

  parent reply	other threads:[~2022-02-24  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  3:40 What's cooking in git.git (Feb 2022, #06; Wed, 23) Junio C Hamano
2022-02-24  9:08 ` ab/commit-plug-leaks + ab/diff-free-more (was: What's cooking in git.git (Feb 2022, #06; Wed, 23)) Ævar Arnfjörð Bjarmason
2022-02-24 23:38   ` ab/commit-plug-leaks + ab/diff-free-more Junio C Hamano
2022-02-24  9:11 ` Ævar Arnfjörð Bjarmason [this message]
2022-02-24  9:18 ` ab/object-file-api-updates (was: What's cooking in git.git (Feb 2022, #06; Wed, 23)) Ævar Arnfjörð Bjarmason
2022-02-24 17:48 ` ar/submodule-update (wa " Glen Choo
2022-02-24 19:55   ` Junio C Hamano
2022-02-24 19:11 ` jc/cat-file-batch-commands (was: " John Cai

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=220224.86fso8aao1.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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