From: Linus Arver <linusa@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #09; Tue, 27)
Date: Thu, 29 Feb 2024 15:56:55 -0800 [thread overview]
Message-ID: <owlyil264yew.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <xmqqjzmpm9b8.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> [...]
>
> * la/trailer-api (2024-02-16) 9 commits
> (merged to 'next' on 2024-02-21 at 631e28bbbc)
> + format_trailers_from_commit(): indirectly call trailer_info_get()
> + format_trailer_info(): move "fast path" to caller
> + format_trailers(): use strbuf instead of FILE
> + trailer_info_get(): reorder parameters
> + trailer: start preparing for formatting unification
> + trailer: move interpret_trailers() to interpret-trailers.c
> + trailer: prepare to expose functions as part of API
> + shortlog: add test for de-duplicating folded trailers
> + trailer: free trailer_info _after_ all related usage
>
> Code clean-up.
>
> Will merge to 'master'.
> source: <pull.1632.v5.git.1708124950.gitgitgadget@gmail.com>
Doh, please wait for my v6 reroll (will send to the list in the next
half hour) to clean up the commit messages. Thanks.
next prev parent reply other threads:[~2024-02-29 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 5:44 What's cooking in git.git (Feb 2024, #09; Tue, 27) Junio C Hamano
2024-02-28 13:38 ` Philippe Blain
2024-02-28 17:25 ` Junio C Hamano
2024-02-29 23:56 ` Linus Arver [this message]
2024-03-01 2:02 ` Junio C Hamano
2024-03-01 16:16 ` Junio C Hamano
2024-03-08 19:11 ` Linus Arver
2024-03-01 10:54 ` Karthik Nayak
2024-03-01 16:21 ` Junio C Hamano
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=owlyil264yew.fsf@fine.c.googlers.com \
--to=linusa@google.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 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.