Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com>
Subject: Re: [PATCH v4] builtin/add.c: replace run_command() with direct apply_all_patches() call
Date: Wed, 26 Aug 2026 10:16:02 -0700	[thread overview]
Message-ID: <xmqqbjaoiyzx.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8q6to4em.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 29 Jul 2026 14:46:25 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Now the way "apply" API is used in this new code path should be
> pretty much parallel to existing "git apply" and "git am" code
> paths, we should be fine.  I do not use "git add -e", but those who
> do who may care more more deeply about keeping this feature working
> than I do may want to lend an extra pair of eyes on this patch.

And nobody seems to be interested in seeing this topic move forward,
unfortunately.  After reading the patch again, I think this is safe
and correct, and if I merge the topic, one of three things can
happen.

 (1) the patch does not regress anything unexpectedly, or

 (2) the patch breaks "add -e" completely but the feature is not
     used by anybody and nobody will notice, or

 (3) the patch breaks "add -e" and the its users will start
     complaining too late.

Reverting a merge would not be too involved as the patch is
small-ish, so even in case (3) it won't be too much trouble to deal
with fallouts.  So let me mark the topic for 'next' for now.

It still is not too late for "add -e" users to interject, though.

Thanks.

      reply	other threads:[~2026-08-26 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 19:26 [PATCH] builtin/add.c: replace run_command() with direct apply_all_patches() call Gatla Vishweshwar Reddy
2026-07-10  6:41 ` Junio C Hamano
2026-07-10  7:32   ` [PATCH v2] " Gatla Vishweshwar Reddy
2026-07-10 18:51     ` Junio C Hamano
2026-07-10 19:58       ` [PATCH v3] " Gatla Vishweshwar Reddy
2026-07-11  4:51         ` Junio C Hamano
2026-07-11  6:06           ` [PATCH v4] " Gatla Vishweshwar Reddy
2026-07-29 21:46             ` Junio C Hamano
2026-08-26 17:16               ` 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=xmqqbjaoiyzx.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=gatlavishweshwarreddy26@gmail.com \
    --cc=git@vger.kernel.org \
    /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