From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2026, #01)
Date: Thu, 09 Apr 2026 13:09:22 -0700 [thread overview]
Message-ID: <xmqqmrzbsxot.fsf@gitster.g> (raw)
In-Reply-To: <1c0e5ba9-9623-4e7f-b4e7-f7e3343ad94e@web.de> ("René Scharfe"'s message of "Thu, 9 Apr 2026 21:54:29 +0200")
René Scharfe <l.s.r@web.de> writes:
> On 4/2/26 1:42 AM, Junio C Hamano wrote:
>> * rs/use-strvec-pushv (2026-03-24) 2 commits
>> (merged to 'next' on 2026-03-24 at 7c6487dcaf)
>> + use strvec_pushv() to add another strvec
>> + Merge branch 'ps/build-tweaks' into rs/use-strvec-pushv
>>
>> Code paths that loop over another array to push each element into a
>> strvec have been rewritten to use strvec_pushv() instead.
>> source: <084f3b43-91ac-4553-8305-03944e97eaa6@web.de>
>
> Curious:
>
> commit 250e977a2b0aa8cc1c8063c64c44597a166e79f5
> Author: Junio C Hamano <gitster@pobox.com>
> Date: Tue Mar 24 12:26:58 2026 -0700
>
> use strvec_pushv() to add another strvec
>
> Add and apply a semantic patch that simplifies the code by letting
> strvec_pushv() append the items of a second strvec instead of pushing
> them one by one.
>
> Suggested-by: Junio C Hamano <gitster@pobox.com>
> Signed-off-by: René Scharfe <l.s.r@web.de>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>
> I guess you became the author when you resolved the merge conflict
> caused by moving contrib/coccinelle/ to tools/?
>
> René
Curious indeed, thanks for noticing, and sorry for the mistake.
prev parent reply other threads:[~2026-04-09 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 23:42 What's cooking in git.git (Apr 2026, #01) Junio C Hamano
2026-04-02 6:57 ` Patrick Steinhardt
2026-04-09 19:54 ` René Scharfe
2026-04-09 20:09 ` 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=xmqqmrzbsxot.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.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 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.