From: Ben Knoble <ben.knoble@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH] add -i: hide init/clear_add_i_state() functions
Date: Fri, 30 Oct 2026 17:35:20 -0400 [thread overview]
Message-ID: <EDD8FC7B-91B4-49CA-AE6B-3475E03EF786@gmail.com> (raw)
In-Reply-To: <xmqqv76jxl22.fsf@gitster.g>
> Le 30 oct. 2026 à 11:30, Junio C Hamano <gitster@pobox.com> a écrit :
>
> Patrick Steinhardt <ps@pks.im> writes:
>
>>> On Wed, Oct 28, 2026 at 12:57:51PM -0700, Junio C Hamano wrote:
>>> The "add -i" machinery is encapsulated in run_add_i() function,
>>> which uses init_add_i_state() to initialize the machinery, does its
>>> thing, and clear_add_i_state() to tear it down. External callers
>>> have no need to call anything other than run_add_i().
>>>
>>> Make init/clear_add_i_state() file-scope static functions, and
>>> "struct add_i_state" type as well.
>>
>> Nice cleanup. For historical context, these declarations are not needed
>> anymore starting with d51b61f5dab (add-patch: remove dependency on
>> "add-interactive" subsystem, 2026-03-02).
>
> Thanks. I did not notice that I gave a backstory for the other
> three commits but apparently did so without digging into the history
> for this one.
>
> By the way, I queued the patches sent to the list on a branch (I
> initially made them on a detached HEAD without keeping a local copy
> after sending them out) and tried 'git history reword' to update
> this one, but it seems it does not honor the notes.rewriteref
> configuration variable. I wonder if this is a known limitation, or
> a deliberate design.
Indeed. I believe it is a known limitation (one I would love to
lift, but will probably not dedicate time to produce code soon). Still, I’ll help
in the usual ways if I can ;)
prev parent reply other threads:[~2026-10-30 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 19:57 [PATCH] add -i: hide init/clear_add_i_state() functions Junio C Hamano
2026-10-28 20:48 ` Ben Knoble
2026-10-30 9:38 ` Patrick Steinhardt
2026-10-30 15:30 ` Junio C Hamano
2026-10-30 21:35 ` Ben Knoble [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=EDD8FC7B-91B4-49CA-AE6B-3475E03EF786@gmail.com \
--to=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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