From: Phillip Wood <phillip.wood123@gmail.com>
To: "Rubén Justo" <rjusto@gmail.com>, "Git List" <git@vger.kernel.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2 0/2] improve interactive-patch
Date: Tue, 26 Mar 2024 14:37:50 +0000 [thread overview]
Message-ID: <59f19783-a663-449d-a1ef-3a9ebc43cc59@gmail.com> (raw)
In-Reply-To: <6f2ed406-2152-476b-b463-3010afe7e11e@gmail.com>
Hi Rubén
On 26/03/2024 00:15, Rubén Justo wrote:
> Let's reduce the verbosity in the interactive-patch process, in order to
> make it less confusing.
I think this is a good idea, I've left a few comments on the patches.
Best Wishes
Phillip
> Rubén Justo (2):
> add-patch: introduce 'p' in interactive-patch
> add-patch: do not print hunks repeatedly
>
> Documentation/git-add.txt | 1 +
> add-patch.c | 20 +++++++++++++++-----
> t/t3701-add-interactive.sh | 22 +++++++++++-----------
> 3 files changed, 27 insertions(+), 16 deletions(-)
>
> Range-diff against v1:
> 1: 48a2c63b78 ! 1: 5e319f439d add-patch: introduce 'p' in interactive-patch
> @@ Commit message
>
> Signed-off-by: Rubén Justo <rjusto@gmail.com>
>
> + ## Documentation/git-add.txt ##
> +@@ Documentation/git-add.txt: patch::
> + K - leave this hunk undecided, see previous hunk
> + s - split the current hunk into smaller hunks
> + e - manually edit the current hunk
> ++ p - print again the current hunk
> + ? - print help
> + +
> + After deciding the fate for all hunks, if there is any hunk
> +
> ## add-patch.c ##
> @@ add-patch.c: N_("j - leave this hunk undecided, see next undecided hunk\n"
> "/ - search for a hunk matching the given regex\n"
> @@ add-patch.c: static int patch_update_file(struct add_p_state *s,
> goto soft_increment;
> }
> + } else if (s->answer.buf[0] == 'p') {
> -+ /* nothing to do */
> ++ /* nothing special is needed */
> } else {
> const char *p = _(help_patch_remainder), *eol = p;
>
> 2: 1730493096 ! 2: 1177bfeae4 add-patch: do not print hunks repeatedly
> @@ Commit message
> g - select a hunk to go to
> / - search for a hunk matching the given regex
> e - manually edit the current hunk
> + p - print again the current hunk
> ? - print help
> @@ -1394,7 +1394,7 @@ N_("j - leave this hunk undecided, see next undecided hunk\n"
> static int patch_update_file(struct add_p_state *s,
> @@ add-patch.c: static int patch_update_file(struct add_p_state *s,
> goto soft_increment;
> }
> } else if (s->answer.buf[0] == 'p') {
> -- /* nothing to do */
> +- /* nothing special is needed */
> + prev_hunk_index = -1;
> } else {
> const char *p = _(help_patch_remainder), *eol = p;
next prev parent reply other threads:[~2024-03-26 14:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 20:59 [PATCH 0/2] improve interactive-patch Rubén Justo
2024-03-25 21:05 ` [PATCH 1/2] add-patch: introduce 'p' in interactive-patch Rubén Justo
2024-03-25 21:38 ` Junio C Hamano
2024-03-25 23:15 ` Rubén Justo
2024-03-25 23:42 ` Junio C Hamano
2024-03-25 21:07 ` [PATCH 2/2] add-patch: do not print hunks repeatedly Rubén Justo
2024-03-25 21:34 ` Junio C Hamano
2024-03-26 0:15 ` [PATCH v2 0/2] improve interactive-patch Rubén Justo
2024-03-26 0:17 ` [PATCH v2 1/2] add-patch: introduce 'p' in interactive-patch Rubén Justo
2024-03-26 14:38 ` Phillip Wood
2024-03-26 18:40 ` Rubén Justo
2024-03-27 10:55 ` Phillip Wood
2024-03-26 0:17 ` [PATCH v2 2/2] add-patch: do not print hunks repeatedly Rubén Justo
2024-03-26 14:39 ` Phillip Wood
2024-03-26 18:46 ` Rubén Justo
2024-03-27 11:06 ` Phillip Wood
2024-03-28 0:39 ` Rubén Justo
2024-03-26 14:37 ` Phillip Wood [this message]
2024-03-26 15:31 ` [PATCH v2 0/2] improve interactive-patch Junio C Hamano
2024-03-26 18:48 ` Rubén Justo
2024-03-26 19:13 ` Junio C Hamano
2024-03-26 20:26 ` Rubén Justo
2024-03-29 19:26 ` Rubén Justo
2024-03-29 19:48 ` Dragan Simic
2024-03-30 13:49 ` Rubén Justo
2024-03-30 17:06 ` Junio C Hamano
2024-03-27 11:14 ` Phillip Wood
2024-03-27 15:43 ` Junio C Hamano
2024-03-27 16:14 ` Phillip Wood
2024-03-28 1:03 ` Rubén Justo
2024-03-26 18:46 ` Rubén Justo
2024-03-28 1:10 ` [PATCH v3 " Rubén Justo
2024-03-28 1:12 ` [PATCH v3 1/2] add-patch: introduce 'p' in interactive-patch Rubén Justo
2024-03-28 14:45 ` Junio C Hamano
2024-03-28 1:12 ` [PATCH v3 2/2] add-patch: do not print hunks repeatedly Rubén Justo
2024-03-28 14:46 ` Junio C Hamano
2024-03-29 3:49 ` Rubén Justo
2024-03-29 3:56 ` [PATCH v4 0/2] improve interactive-patch Rubén Justo
2024-03-29 3:58 ` [PATCH v4 1/2] add-patch: introduce 'p' in interactive-patch Rubén Justo
2024-03-29 3:58 ` [PATCH v4 2/2] add-patch: do not print hunks repeatedly Rubén Justo
2024-03-29 10:41 ` phillip.wood123
2024-03-29 11:37 ` Rubén Justo
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=59f19783-a663-449d-a1ef-3a9ebc43cc59@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=rjusto@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).