threads / patch / 66695

patchadd -i: hide init/clear_add_i_state() functions

Subject: [PATCH] add -i: hide init/clear_add_i_state() functions

## tl;dr

6 messages between Oct 28, 2026 and Nov 2, 2026. Diffs are folded; open one to read it.

replies: 5people: 3as markdown or json

Junio C Hamano· Oct 28, 2026, 19:57 UTC · lore

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.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 add-interactive.c | 11 ++++++++---
 add-interactive.h |  9 ---------
 2 files changed, 8 insertions(+), 12 deletions(-)
Show changes to 2 files +8 −12

add-interactive.c, add-interactive.h

diff --git a/add-interactive.c b/add-interactive.c
index 3cf8a1dbf8..9a00daf9f9 100644
--- a/add-interactive.c
+++ b/add-interactive.c
@@ -19,14 +19,19 @@
 #include "prompt.h"
 #include "tree.h"
 
-void init_add_i_state(struct add_i_state *s, struct repository *r,
-		      struct interactive_options *opts)
+struct add_i_state {
+	struct repository *r;
+	struct interactive_config cfg;
+};
+
+static void init_add_i_state(struct add_i_state *s, struct repository *r,
+			     struct interactive_options *opts)
 {
 	s->r = r;
 	interactive_config_init(&s->cfg, r, opts);
 }
 
-void clear_add_i_state(struct add_i_state *s)
+static void clear_add_i_state(struct add_i_state *s)
 {
 	interactive_config_clear(&s->cfg);
 	memset(s, 0, sizeof(*s));
diff --git a/add-interactive.h b/add-interactive.h
index eefa2edc7c..47f67ede82 100644
--- a/add-interactive.h
+++ b/add-interactive.h
@@ -6,15 +6,6 @@
 struct pathspec;
 struct repository;
 
-struct add_i_state {
-	struct repository *r;
-	struct interactive_config cfg;
-};
-
-void init_add_i_state(struct add_i_state *s, struct repository *r,
-		      struct interactive_options *opts);
-void clear_add_i_state(struct add_i_state *s);
-
 int run_add_i(struct repository *r, const struct pathspec *ps,
 	      struct interactive_options *opts);
 
-- 
2.56.0-433-ga9209adf11
Ben Knoble· Oct 28, 2026, 20:48 UTC · re: Junio C Hamano · lore

Re: [PATCH] add -i: hide init/clear_add_i_state() functions

Show 9 quoted lines
> Le 28 oct. 2026 à 16:22, Junio C Hamano <gitster@pobox.com> a écrit :
> 
> 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.
Yep, narrower interfaces are easier for programmers to consume, thanks. 
Show 55 quoted lines
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> add-interactive.c | 11 ++++++++---
> add-interactive.h |  9 ---------
> 2 files changed, 8 insertions(+), 12 deletions(-)
> 
> diff --git a/add-interactive.c b/add-interactive.c
> index 3cf8a1dbf8..9a00daf9f9 100644
> --- a/add-interactive.c
> +++ b/add-interactive.c
> @@ -19,14 +19,19 @@
> #include "prompt.h"
> #include "tree.h"
> 
> -void init_add_i_state(struct add_i_state *s, struct repository *r,
> -              struct interactive_options *opts)
> +struct add_i_state {
> +    struct repository *r;
> +    struct interactive_config cfg;
> +};
> +
> +static void init_add_i_state(struct add_i_state *s, struct repository *r,
> +                 struct interactive_options *opts)
> {
>    s->r = r;
>    interactive_config_init(&s->cfg, r, opts);
> }
> 
> -void clear_add_i_state(struct add_i_state *s)
> +static void clear_add_i_state(struct add_i_state *s)
> {
>    interactive_config_clear(&s->cfg);
>    memset(s, 0, sizeof(*s));
> diff --git a/add-interactive.h b/add-interactive.h
> index eefa2edc7c..47f67ede82 100644
> --- a/add-interactive.h
> +++ b/add-interactive.h
> @@ -6,15 +6,6 @@
> struct pathspec;
> struct repository;
> 
> -struct add_i_state {
> -    struct repository *r;
> -    struct interactive_config cfg;
> -};
> -
> -void init_add_i_state(struct add_i_state *s, struct repository *r,
> -              struct interactive_options *opts);
> -void clear_add_i_state(struct add_i_state *s);
> -
> int run_add_i(struct repository *r, const struct pathspec *ps,
>          struct interactive_options *opts);
> 
> --
> 2.56.0-433-ga9209adf11
And this matches the log message.
I did not check for callers, but I assume you did your due-diligence there ;) 
Patrick Steinhardt· Oct 30, 2026, 09:38 UTC · re: Junio C Hamano · lore

Re: [PATCH] add -i: hide init/clear_add_i_state() functions

On Wed, Oct 28, 2026 at 12:57:51PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> 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!
Patrick
Junio C Hamano· Oct 30, 2026, 15:30 UTC · re: Patrick Steinhardt · lore

Re: [PATCH] add -i: hide init/clear_add_i_state() functions

Patrick Steinhardt <ps@pks.im> writes:
Show 12 quoted lines
> 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.

Thanks.
Ben Knoble· Oct 30, 2026, 21:35 UTC · re: Junio C Hamano · lore

Re: [PATCH] add -i: hide init/clear_add_i_state() functions

Show 27 quoted lines
> 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 ;)

Patrick Steinhardt· Nov 2, 2026, 08:42 UTC · re: Ben Knoble · lore

Re: [PATCH] add -i: hide init/clear_add_i_state() functions

On Fri, Oct 30, 2026 at 05:35:20PM -0400, Ben Knoble wrote:
Show 32 quoted lines
> 
> > 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 ;)

Yeah, it's a limitation and not a design decision. I'd be happy to review any such patch series, as I'm also a bit short on time recently. Meanwhile I've also created an issue in our bug tracker, so we may pick this up in the next release cycle.

Patrick

← back to recent threads