From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Stefan Haller <lists@haller-berlin.de>,
Phillip Wood <phillip.wood123@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Glen Choo <chooglen@google.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH v4 0/7] rebase -i: impove handling of failed commands
Date: Thu, 7 Sep 2023 11:56:39 +0200 (CEST) [thread overview]
Message-ID: <6b927687-cf6e-d73e-78fb-bd4f46736928@gmx.de> (raw)
In-Reply-To: <pull.1492.v4.git.1694013771.gitgitgadget@gmail.com>
Hi Phillip,
On Wed, 6 Sep 2023, Phillip Wood via GitGitGadget wrote:
> Range-diff vs v3:
>
> 1: 1ab1ad2ef07 ! 1: ae4f873b3d0 rebase -i: move unlink() calls
> @@ Metadata
> ## Commit message ##
> rebase -i: move unlink() calls
>
> - At the start of each iteration the loop that picks commits removes
> - state files from the previous pick. However some of these are only
> - written if there are conflicts and so we break out of the loop after
> - writing them. Therefore they only need to be removed when the rebase
> - continues, not in each iteration.
> + At the start of each iteration the loop that picks commits removes the
> + state files from the previous pick. However some of these files are only
> + written if there are conflicts in which case we exit the loop before the
> + end of the loop body. Therefore they only need to be removed when the
> + rebase continues, not at the start of each iteration.
>
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> 2: e2a758eb4a5 ! 2: f540ed1d607 rebase -i: remove patch file after conflict resolution
> @@ Commit message
> now used in two different places rebase_path_patch() is added and used
> to obtain the path for the patch.
>
> + To construct the path write_patch() previously used get_dir() which
> + returns different paths depending on whether we're rebasing or
> + cherry-picking/reverting. As this function is only called when
> + rebasing it is safe to use a hard coded string for the directory
> + instead. An assertion is added to make sure we don't starting calling
> + this function when cherry-picking in the future.
> +
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> ## sequencer.c ##
> @@ sequencer.c: static GIT_PATH_FUNC(rebase_path_amend, "rebase-merge/amend")
> * For the post-rewrite hook, we make a list of rewritten commits and
> * their new sha1s. The rewritten-pending list keeps the sha1s of
> @@ sequencer.c: static int make_patch(struct repository *r,
> + char hex[GIT_MAX_HEXSZ + 1];
> + int res = 0;
> +
> ++ if (!is_rebase_i(opts))
> ++ BUG("make_patch should only be called when rebasing");
> ++
> + oid_to_hex_r(hex, &commit->object.oid);
> + if (write_message(hex, strlen(hex), rebase_path_stopped_sha(), 1) < 0)
> return -1;
> res |= write_rebase_head(&commit->object.oid);
>
> 3: 8f6c0e40567 ! 3: 818bdaf772d sequencer: use rebase_path_message()
> @@ Commit message
> made function to get the path name instead. This was the last
> remaining use of the strbuf so remove it as well.
>
> + As with the previous patch we now use a hard coded string rather than
> + git_dir() when constructing the path. This is safe for the same
> + reason (make_patch() is only called when rebasing) and is protected by
> + the assertion added in the previous patch.
> +
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> ## sequencer.c ##
> 4: a1fad70f4b9 = 4: bd67765a864 sequencer: factor out part of pick_commits()
> 5: df401945866 ! 5: f6f330f7063 rebase: fix rewritten list for failed pick
> @@ Commit message
> disabled the user will see the messages from the merge machinery
> detailing the problem.
>
> - To simplify writing REBASE_HEAD in this case pick_one_commit() is
> - modified to avoid duplicating the code that adds the failed command
> - back into the todo list.
> + The code to add a failed command back into the todo list is duplicated
> + between pick_one_commit() and the loop in pick_commits(). Both sites
> + print advice about the command being rescheduled, decrement the current
> + item and save the todo list. To avoid duplicating this code
> + pick_one_commit() is modified to set a flag to indicate that the command
> + should be rescheduled in the main loop. This simplifies things as only
> + the remaining copy of the code needs to be modified to set REBASE_HEAD
> + rather than calling error_with_patch().
>
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> 6: 2ed7cbe5fff = 6: 0ca5fccca17 rebase --continue: refuse to commit after failed command
> 7: bbe0afde512 = 7: 8d5f6d51e19 rebase -i: fix adding failed command to the todo list
Thank you for indulging me. This iteration looks good to me!
Ciao,
Johannes
next prev parent reply other threads:[~2023-09-07 20:26 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 14:48 [PATCH] rebase -i: do not update "done" when rescheduling command Phillip Wood via GitGitGadget
2023-03-20 7:29 ` Stefan Haller
2023-03-20 17:46 ` Junio C Hamano
2023-03-24 10:50 ` Phillip Wood
2023-03-24 15:49 ` Junio C Hamano
2023-03-24 16:22 ` Phillip Wood
2023-03-27 7:04 ` Johannes Schindelin
2023-08-03 12:56 ` Phillip Wood
2023-08-23 8:54 ` Johannes Schindelin
2023-04-21 14:57 ` [PATCH v2 0/6] rebase -i: impove handling of failed commands Phillip Wood via GitGitGadget
2023-04-21 14:57 ` [PATCH v2 1/6] rebase -i: move unlink() calls Phillip Wood via GitGitGadget
2023-04-21 17:22 ` Junio C Hamano
2023-04-27 10:15 ` Phillip Wood
2023-04-21 14:57 ` [PATCH v2 2/6] rebase -i: remove patch file after conflict resolution Phillip Wood via GitGitGadget
2023-04-21 19:01 ` Junio C Hamano
2023-04-27 10:17 ` Phillip Wood
2023-06-21 20:14 ` Glen Choo
2023-07-14 10:08 ` Phillip Wood
2023-07-14 16:51 ` Junio C Hamano
2023-07-17 15:39 ` Phillip Wood
2023-04-21 14:57 ` [PATCH v2 3/6] sequencer: factor out part of pick_commits() Phillip Wood via GitGitGadget
2023-04-21 19:12 ` Eric Sunshine
2023-04-21 19:31 ` Junio C Hamano
2023-04-21 20:00 ` Phillip Wood
2023-04-21 21:21 ` Junio C Hamano
2023-04-21 14:57 ` [PATCH v2 4/6] rebase --continue: refuse to commit after failed command Phillip Wood via GitGitGadget
2023-04-21 19:14 ` Eric Sunshine
2023-04-21 21:05 ` Junio C Hamano
2023-06-21 20:35 ` Glen Choo
2023-04-21 14:57 ` [PATCH v2 5/6] rebase: fix rewritten list for failed pick Phillip Wood via GitGitGadget
2023-06-21 20:49 ` Glen Choo
2023-07-25 15:42 ` Phillip Wood
2023-07-25 16:46 ` Glen Choo
2023-07-26 13:08 ` Phillip Wood
2023-07-26 17:48 ` Glen Choo
2023-07-28 13:19 ` Phillip Wood
2023-04-21 14:57 ` [PATCH v2 6/6] rebase -i: fix adding failed command to the todo list Phillip Wood via GitGitGadget
2023-06-21 20:59 ` Glen Choo
2023-04-21 16:56 ` [PATCH v2 0/6] rebase -i: impove handling of failed commands Junio C Hamano
2023-06-21 20:07 ` Glen Choo
2023-08-01 15:23 ` [PATCH v3 0/7] " Phillip Wood via GitGitGadget
2023-08-01 15:23 ` [PATCH v3 1/7] rebase -i: move unlink() calls Phillip Wood via GitGitGadget
2023-08-01 17:22 ` Junio C Hamano
2023-08-01 18:42 ` Phillip Wood
2023-08-01 19:31 ` Junio C Hamano
2023-08-01 15:23 ` [PATCH v3 2/7] rebase -i: remove patch file after conflict resolution Phillip Wood via GitGitGadget
2023-08-01 17:23 ` Junio C Hamano
2023-08-01 18:47 ` Phillip Wood
2023-08-01 15:23 ` [PATCH v3 3/7] sequencer: use rebase_path_message() Phillip Wood via GitGitGadget
2023-08-01 17:23 ` Junio C Hamano
2023-08-01 18:49 ` Phillip Wood
2023-08-02 22:02 ` Junio C Hamano
2023-08-01 15:23 ` [PATCH v3 4/7] sequencer: factor out part of pick_commits() Phillip Wood via GitGitGadget
2023-08-23 8:55 ` Johannes Schindelin
2023-08-01 15:23 ` [PATCH v3 5/7] rebase: fix rewritten list for failed pick Phillip Wood via GitGitGadget
2023-08-23 8:55 ` Johannes Schindelin
2023-09-04 14:31 ` Phillip Wood
2023-08-01 15:23 ` [PATCH v3 6/7] rebase --continue: refuse to commit after failed command Phillip Wood via GitGitGadget
2023-08-23 9:01 ` Johannes Schindelin
2023-09-04 14:37 ` Phillip Wood
2023-09-05 11:17 ` Johannes Schindelin
2023-09-05 14:57 ` Junio C Hamano
2023-09-05 15:25 ` Phillip Wood
2023-08-01 15:23 ` [PATCH v3 7/7] rebase -i: fix adding failed command to the todo list Phillip Wood via GitGitGadget
2023-08-02 22:10 ` [PATCH v3 0/7] rebase -i: impove handling of failed commands Junio C Hamano
2023-08-03 13:06 ` Phillip Wood
2023-08-09 13:08 ` Phillip Wood
2023-08-07 20:16 ` Glen Choo
2023-08-09 10:06 ` Phillip Wood
2023-09-06 15:22 ` [PATCH v4 " Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 1/7] rebase -i: move unlink() calls Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 2/7] rebase -i: remove patch file after conflict resolution Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 3/7] sequencer: use rebase_path_message() Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 4/7] sequencer: factor out part of pick_commits() Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 5/7] rebase: fix rewritten list for failed pick Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 6/7] rebase --continue: refuse to commit after failed command Phillip Wood via GitGitGadget
2023-09-06 15:22 ` [PATCH v4 7/7] rebase -i: fix adding failed command to the todo list Phillip Wood via GitGitGadget
2023-09-06 21:01 ` [PATCH v4 0/7] rebase -i: impove handling of failed commands Junio C Hamano
2023-09-07 9:56 ` Johannes Schindelin [this message]
2023-09-07 20:33 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b927687-cf6e-d73e-78fb-bd4f46736928@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=lists@haller-berlin.de \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).