From: Phillip Wood <phillip.wood123@gmail.com> To: ZheNing Hu via GitGitGadget <gitgitgadget@gmail.com>, git@vger.kernel.org Cc: "Junio C Hamano" <gitster@pobox.com>, "Christian Couder" <christian.couder@gmail.com>, "Hariom Verma" <hariom18599@gmail.com>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, "Han-Wen Nienhuys" <hanwen@google.com>, "Ramkumar Ramachandra" <artagnon@gmail.com>, "Felipe Contreras" <felipe.contreras@gmail.com>, "ZheNing Hu" <adlternative@gmail.com> Subject: Re: [PATCH 2/2] [GSOC] cherry-pick: use better advice message Date: Sun, 1 Aug 2021 11:14:32 +0100 [thread overview] Message-ID: <0a2ab793-de4d-d8d1-4d1d-a018fa0f252c@gmail.com> (raw) In-Reply-To: <7e1ed49728df8dab771d77f1a076f0fa30975718.1627714878.git.gitgitgadget@gmail.com> On 31/07/2021 08:01, ZheNing Hu via GitGitGadget wrote: > From: ZheNing Hu <adlternative@gmail.com> > > In the past, git cherry-pick would print such advice when > there was a conflict: > > hint: after resolving the conflicts, mark the corrected paths > hint: with 'git add <paths>' or 'git rm <paths>' > hint: and commit the result with 'git commit' > > But in fact, when we want to cherry-pick multiple commits, > we should not use "git commit" after resolving conflicts, which > will make Git generate some errors. We should recommend users to > use `git cherry-pick --continue`, `git cherry-pick --abort`, just > like git rebase does. > > This is the improved advice: > > hint: Resolve all conflicts manually, mark them as resolved with > hint: "git add/rm <conflicted_files>", then run "git cherry-pick \ > --continue". > hint: You can instead skip this commit: run "git cherry-pick --skip". > hint: To abort and get back to the state before "git cherry-pick", > hint: run "git cherry-pick --abort". This new wording matches what we have for rebase which is good, I am slightly worried that the lines end up being quite long though they are just under 80 characters. It might be worth splitting the line that mentions running "git cherry-pick --continue" so it is a bit shorter. Best Wishes Phillip > Mentored-by: Christian Couder <christian.couder@gmail.com> > Mentored-by Hariom Verma <hariom18599@gmail.com>: > Helped-by: Phillip Wood <phillip.wood@dunelm.org.uk> > Hepled-by: Junio C Hamano <gitster@pobox.com> > Signed-off-by: ZheNing Hu <adlternative@gmail.com> > --- > sequencer.c | 9 ++++++++- > t/t3507-cherry-pick-conflict.sh | 15 ++++++++++----- > 2 files changed, 18 insertions(+), 6 deletions(-) > > diff --git a/sequencer.c b/sequencer.c > index 83cf6a5da3c..f6e9d1fddd8 100644 > --- a/sequencer.c > +++ b/sequencer.c > @@ -404,7 +404,14 @@ static void print_advice(struct replay_opts *opts, int show_hint) > if (msg) { > advise("%s\n", msg); > } else if (show_hint) { > - if (opts->no_commit) > + if (opts->action == REPLAY_PICK) { > + advise(_("Resolve all conflicts manually, mark them as resolved with\n" > + "\"git add/rm <conflicted_files>\", then run \"git cherry-pick --continue\".\n" > + "You can instead skip this commit: run \"git cherry-pick --skip\".\n" > + "To abort and get back to the state before \"git cherry-pick\",\n" > + "run \"git cherry-pick --abort\".")); > + > + } else if (opts->no_commit) > advise(_("after resolving the conflicts, mark the corrected paths\n" > "with 'git add <paths>' or 'git rm <paths>'")); > else > diff --git a/t/t3507-cherry-pick-conflict.sh b/t/t3507-cherry-pick-conflict.sh > index f17621d1915..2cc3977f5a6 100755 > --- a/t/t3507-cherry-pick-conflict.sh > +++ b/t/t3507-cherry-pick-conflict.sh > @@ -53,9 +53,11 @@ test_expect_success 'advice from failed cherry-pick' " > picked=\$(git rev-parse --short picked) && > cat <<-EOF >expected && > error: could not apply \$picked... picked > - hint: after resolving the conflicts, mark the corrected paths > - hint: with 'git add <paths>' or 'git rm <paths>' > - hint: and commit the result with 'git commit' > + hint: Resolve all conflicts manually, mark them as resolved with > + hint: \"git add/rm <conflicted_files>\", then run \"git cherry-pick --continue\". > + hint: You can instead skip this commit: run \"git cherry-pick --skip\". > + hint: To abort and get back to the state before \"git cherry-pick\", > + hint: run \"git cherry-pick --abort\". > EOF > test_must_fail git cherry-pick picked 2>actual && > > @@ -68,8 +70,11 @@ test_expect_success 'advice from failed cherry-pick --no-commit' " > picked=\$(git rev-parse --short picked) && > cat <<-EOF >expected && > error: could not apply \$picked... picked > - hint: after resolving the conflicts, mark the corrected paths > - hint: with 'git add <paths>' or 'git rm <paths>' > + hint: Resolve all conflicts manually, mark them as resolved with > + hint: \"git add/rm <conflicted_files>\", then run \"git cherry-pick --continue\". > + hint: You can instead skip this commit: run \"git cherry-pick --skip\". > + hint: To abort and get back to the state before \"git cherry-pick\", > + hint: run \"git cherry-pick --abort\". > EOF > test_must_fail git cherry-pick --no-commit picked 2>actual && > >
next prev parent reply other threads:[~2021-08-01 10:14 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-31 7:01 [PATCH 0/2] [GSOC] cherry-pick: fix bug when used with GIT_CHERRY_PICK_HELP ZheNing Hu via GitGitGadget 2021-07-31 7:01 ` [PATCH 1/2] " ZheNing Hu via GitGitGadget 2021-08-01 10:09 ` Phillip Wood 2021-08-02 13:34 ` ZheNing Hu 2021-07-31 7:01 ` [PATCH 2/2] [GSOC] cherry-pick: use better advice message ZheNing Hu via GitGitGadget 2021-08-01 10:14 ` Phillip Wood [this message] 2021-08-02 13:35 ` ZheNing Hu 2021-08-03 1:16 ` [PATCH v2 0/2] [GSOC] cherry-pick: fix bug when used with GIT_CHERRY_PICK_HELP ZheNing Hu via GitGitGadget 2021-08-03 1:16 ` [PATCH v2 1/2] " ZheNing Hu via GitGitGadget 2021-08-03 22:36 ` Junio C Hamano 2021-08-04 8:35 ` ZheNing Hu 2021-08-04 10:10 ` Phillip Wood 2021-08-04 17:31 ` Junio C Hamano 2021-08-05 5:36 ` ZheNing Hu 2021-08-03 1:16 ` [PATCH v2 2/2] [GSOC] cherry-pick: use better advice message ZheNing Hu via GitGitGadget 2021-08-05 5:48 ` [PATCH v3] " ZheNing Hu via GitGitGadget 2021-08-11 10:00 ` Phillip Wood 2021-08-13 8:08 ` ZheNing Hu 2021-08-13 20:14 ` Junio C Hamano 2021-08-14 2:07 ` ZheNing Hu 2021-08-17 10:09 ` Phillip Wood 2021-08-14 10:27 ` [PATCH v4] " ZheNing Hu via GitGitGadget 2021-08-14 20:32 ` Junio C Hamano 2021-08-15 12:48 ` ZheNing Hu 2021-08-16 0:55 ` [PATCH v5] " ZheNing Hu via GitGitGadget 2021-08-18 9:51 ` Phillip Wood 2021-08-19 1:55 ` ZheNing Hu 2021-08-19 2:07 ` ZheNing Hu 2021-08-19 5:51 ` [PATCH v6] " ZheNing Hu via GitGitGadget 2021-08-19 17:10 ` Junio C Hamano 2021-08-21 1:40 ` ZheNing Hu 2021-08-22 13:08 ` [PATCH v7] " ZheNing Hu via GitGitGadget -- strict thread matches above, loose matches on Subject: below -- 2021-07-29 12:27 [PATCH 0/2] [GSOC] cherry-pick: fix bug when used with GIT_CHERRY_PICK_HELP ZheNing Hu via GitGitGadget 2021-07-29 12:27 ` [PATCH 2/2] [GSOC] cherry-pick: use better advice message ZheNing Hu via GitGitGadget
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=0a2ab793-de4d-d8d1-4d1d-a018fa0f252c@gmail.com \ --to=phillip.wood123@gmail.com \ --cc=adlternative@gmail.com \ --cc=artagnon@gmail.com \ --cc=avarab@gmail.com \ --cc=christian.couder@gmail.com \ --cc=felipe.contreras@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitgitgadget@gmail.com \ --cc=gitster@pobox.com \ --cc=hanwen@google.com \ --cc=hariom18599@gmail.com \ --cc=phillip.wood@dunelm.org.uk \ --subject='Re: [PATCH 2/2] [GSOC] cherry-pick: use better advice message' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.