git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2024, #06; Tue, 14)
Date: Wed, 15 May 2024 13:57:01 +0200	[thread overview]
Message-ID: <CAP8UFD0q1yBm4aG6pmByOxMAvYcbmwfAWkSK=nyCoAAY3qptig@mail.gmail.com> (raw)
In-Reply-To: <xmqqcypo47p7.fsf@gitster.g>

On Tue, May 14, 2024 at 7:36 PM Junio C Hamano <gitster@pobox.com> wrote:

> * la/hide-trailer-info (2024-05-02) 11 commits
>  - trailer unit tests: inspect iterator contents
>  - trailer: document parse_trailers() usage
>  - trailer: retire trailer_info_get() from API
>  - trailer: make trailer_info struct private
>  - trailer: make parse_trailers() return trailer_info pointer
>  - interpret-trailers: access trailer_info with new helpers
>  - sequencer: use the trailer iterator
>  - trailer: teach iterator about non-trailer lines
>  - trailer: add unit tests for trailer iterator
>  - Makefile: sort UNIT_TEST_PROGRAMS
>  - Merge branch 'la/format-trailer-info' into la/hide-trailer-info
>
>  The trailer API has been reshuffled a bit.
>
>  Waiting for a review response.
>  cf. <a75133dc-a0bb-4f61-a616-988f2b4d5688@gmail.com>
>  source: <pull.1696.v4.git.1714625667.gitgitgadget@gmail.com>

Linus replied in the following message:

https://lore.kernel.org/git/CAMo6p=FS3ShvBdutprWBiAVef6A1XjsXB1UJSQBk0s5euN=tog@mail.gmail.com/

Phillip then agreed with Linus that the improvements he suggested
could be done later.

I took a look at Linus' v4 and I am also fine with it. Thanks.

  reply	other threads:[~2024-05-15 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 17:36 What's cooking in git.git (May 2024, #06; Tue, 14) Junio C Hamano
2024-05-15 11:57 ` Christian Couder [this message]
2024-05-15 14:16   ` Junio C Hamano
2024-05-15 19:33 ` Phillip Wood
2024-05-16 16:00 ` René Scharfe

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='CAP8UFD0q1yBm4aG6pmByOxMAvYcbmwfAWkSK=nyCoAAY3qptig@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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).