From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Elijah Newren <newren@gmail.com>, Duy Nguyen <pclouds@gmail.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH 1/2] commit/reset: try to clean up sequencer state
Date: Mon, 8 Apr 2019 15:15:23 +0100 [thread overview]
Message-ID: <1a3cf9ed-69ff-d961-e62b-a38b45913411@gmail.com> (raw)
In-Reply-To: <xmqq36n2yvr8.fsf@gitster-ct.c.googlers.com>
Hi Junio
On 01/04/2019 09:28, Junio C Hamano wrote:
> Phillip Wood <phillip.wood123@gmail.com> writes:
>
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> When cherry-picking or reverting a sequence of commits and if the final
>> pick/revert has conflicts and the user uses `git commit` to commit the
>> conflict resolution and does not run `git cherry-pick --continue` then
>> the sequencer state is left behind. This can cause problems later. In my
>> case I cherry-picked a sequence of commits the last one of which I
>> committed with `git commit` after resolving some conflicts, then a while
>> later, on a different branch I aborted a revert which rewound my HEAD to
>> the end of the cherry-pick sequence on the previous branch.
>
> I've certainly seen this myself. Do you use command line prompt
> support to remind you of the operation in progress? I do, and I
> have a suspicion that it did not help me in this situation by
> ceasing to tell me that I have leftover state files after a manual
> commit of the final step that conflicted and gave control back to
> me.
Same here, the prompt I use just checks for the presence of
CHERRY_PICK_HEAD which disappears after committing.
> And detecting that we are finishing the last step and making sure
> that the state files are removed does sound like the right approach
> to fix it.
>
>> diff --git a/branch.c b/branch.c
>> index 28b81a7e02..9ed60081c1 100644
>> --- a/branch.c
>> +++ b/branch.c
>> @@ -5,6 +5,7 @@
>> #include "refs.h"
>> #include "refspec.h"
>> #include "remote.h"
>> +#include "sequencer.h"
>> #include "commit.h"
>> #include "worktree.h"
>>
>> @@ -339,8 +340,10 @@ void create_branch(struct repository *r,
>>
>> void remove_branch_state(struct repository *r)
>> {
>> - unlink(git_path_cherry_pick_head(r));
>> - unlink(git_path_revert_head(r));
>> + if (!unlink(git_path_cherry_pick_head(r)))
>> + sequencer_post_commit_cleanup();
>> + if (!unlink(git_path_revert_head(r)))
>> + sequencer_post_commit_cleanup();
>
> This and the same one in builtin/commit.c feels a bit iffy. If we
> had CHERRY_PICK_HEAD or REVERT_HEAD and attempted to remove one or
> the other, whether the removal succeeds or fails (perhaps a virus
> scanner on Windows had the file open while we tried to unlink it,
> causing the unlink() to fail), don't we want the clean-up to happen?
Good point, I could add '|| errno == ENOENT' to the if or just use
file_exists() as you suggest below
>> @@ -1678,6 +1680,7 @@ int cmd_commit(int argc, const char **argv, const char *prefix)
>> if (amend && !no_post_rewrite) {
>> commit_post_rewrite(the_repository, current_head, &oid);
>> }
>> +
>
> This is an unrelated change.
Oops I'm not sure where that came from
>> if (!quiet) {
>> unsigned int flags = 0;
>>
>> diff --git a/sequencer.c b/sequencer.c
>> index 0db410d590..028699209f 100644
>> --- a/sequencer.c
>> +++ b/sequencer.c
>> @@ -2220,6 +2220,29 @@ static ssize_t strbuf_read_file_or_whine(struct strbuf *sb, const char *path)
>> return len;
>> }
>>
>> +void sequencer_post_commit_cleanup(void)
>> +{
>> + struct replay_opts opts = REPLAY_OPTS_INIT;
>> + struct strbuf buf = STRBUF_INIT;
>> + const char *eol;
>> + const char *todo_path = git_path_todo_file();
>> +
>> + if (strbuf_read_file(&buf, todo_path, 0) < 0) {
>> + if (errno == ENOENT) {
>> + return;
>> + } else {
>> + error_errno("unable to open '%s'", todo_path);
>> + return;
>> + }
>> + }
>> + /* If there is only one line then we are done */
>> + eol = strchr(buf.buf, '\n');
>> + if (!eol || !eol[1])
>> + sequencer_remove_state(&opts);
>> +
>> + strbuf_release(&buf);
>> +}
>
> I find this helper doing a bit too much and a bit too little at the
> same time. To reduce the iffiness I mentioned earlier, the callers
> would behefit to have a helper that
>
> - notices the need to remove CHERRY_PICK_HEAD or REVERT_HEAD, and
> returns without doing anything if there is no need;
>
> - remove the *_HEAD file.
>
> - detect if we have dealt with the last step, and returns without
> doing any more thing if there are more to do;
>
> - remove the state files.
>
> IOW, replace the existing series of two unlink() calls with a single
> call to the helper.
>
> On the other hand, the bulk of hand-rolled logic to determine if we
> have processed the last step is better done in another helper
> function that helps this helper, i.e.
>
> void sequencer_post_commit_cleanup(struct repo *r)
> {
> int need_cleanup = 0;
>
> if (file_exists(git_path_cherry_pick_head(r)) {
> unlink(git_path_cherry_pick_head(r));
> need_cleanup = 1;
> }
> if (file_exists(git_path_revert_head(r)) {
> unlink(git_path_revert_head(r));
> need_cleanup = 1;
> }
> if (!need_cleanup)
> return;
> if (!have_finished_the_last_pick())
> return;
> sequencer_remove_state(&opts);
> }
>
> as that makes it easier to follow the logic of what is going on at
> this level, while at the same time making the logic in the
> have_finished_the_last_pick() helper easier to read by giving it a
> meaningful name.
Thanks that definitely improves things, I'll send a re-roll
Best Wishes
Phillip
next prev parent reply other threads:[~2019-04-08 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:30 [PATCH 0/2] A couple of cherry-pick related fixes Phillip Wood
2019-03-29 16:30 ` [PATCH 1/2] commit/reset: try to clean up sequencer state Phillip Wood
2019-04-01 8:28 ` Junio C Hamano
2019-04-08 14:15 ` Phillip Wood [this message]
2019-04-01 10:09 ` Duy Nguyen
2019-04-08 15:47 ` Phillip Wood
2019-03-29 16:30 ` [PATCH 2/2] fix cherry-pick/revert status after commit Phillip Wood
2019-04-01 8:34 ` Junio C Hamano
2019-04-08 14:17 ` Phillip Wood
2019-04-16 10:18 ` [PATCH v2 0/2] A couple of cherry-pick related fixes Phillip Wood
2019-04-16 10:18 ` [PATCH v2 1/2] commit/reset: try to clean up sequencer state Phillip Wood
2019-04-17 7:04 ` Junio C Hamano
2019-04-17 12:26 ` Johannes Schindelin
2019-04-17 15:04 ` Phillip Wood
2019-04-16 10:18 ` [PATCH v2 2/2] fix cherry-pick/revert status after commit Phillip Wood
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=1a3cf9ed-69ff-d961-e62b-a38b45913411@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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).