From: ZheNing Hu <adlternative@gmail.com> To: phillip.wood@dunelm.org.uk Cc: "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>, "Git List" <git@vger.kernel.org>, "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> Subject: Re: [PATCH v3] [GSOC] cherry-pick: use better advice message Date: Fri, 13 Aug 2021 16:08:08 +0800 [thread overview] Message-ID: <CAOLTT8QGD08BRuJ5Z8kLdS8gFx+HBeZfsgqotTz0Xch3BNHGPg@mail.gmail.com> (raw) In-Reply-To: <a510722c-d5a2-f00c-dd20-dd7f76da2408@gmail.com> Hi, sorry for the late reply, I am busy processing the patches on the ref-filter side. Phillip Wood <phillip.wood123@gmail.com> 于2021年8月11日周三 下午6:00写道: > > On 05/08/2021 06:48, ZheNing Hu via GitGitGadget wrote: > > From: ZheNing Hu <adlternative@gmail.com> > > [...] > > sequencer.c | 11 +++++++++-- > > t/t3507-cherry-pick-conflict.sh | 17 ++++++++++++----- > > 2 files changed, 21 insertions(+), 7 deletions(-) > > > > diff --git a/sequencer.c b/sequencer.c > > index 0bec01cf38e..7fa91b99870 100644 > > --- a/sequencer.c > > +++ b/sequencer.c > > @@ -403,7 +403,7 @@ static void print_advice(struct repository *r, int show_hint, > > char *msg = getenv("GIT_CHERRY_PICK_HELP"); > > > > if (msg) { > > - fprintf(stderr, "%s\n", msg); > > + advise("%s\n", msg); > > /* > > * A conflict has occurred but the porcelain > > * (typically rebase --interactive) wants to take care > > @@ -415,7 +415,14 @@ static void print_advice(struct repository *r, int show_hint, > > } > > > > if (show_hint) { > > - if (opts->no_commit) > > + if (opts->action == REPLAY_PICK) { > > This changes means we give the wrong advice for 'git cherry-pick > --no-commit'. I think you want to keep the existing clause as the first > one and insert this before the else. The advice itself looks good. It > would be nice to improve the advice for 'git revert' in the same way. > Make sense. > > + advise(_("Resolve all conflicts manually, mark them as resolved with\n" > > + "\"git add/rm <conflicted_files>\", then run\n" > > + "\"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 014001b8f32..d3ed9d7ce0d 100755 > > --- a/t/t3507-cherry-pick-conflict.sh > > +++ b/t/t3507-cherry-pick-conflict.sh > > @@ -53,9 +53,12 @@ test_expect_success 'advice from failed cherry-pick' " > > picked=\$(git rev-parse --short picked) && > > cat <<-EOF >expected && > > If you quote the here doc end marker then there is no substitution in > the here doc so writing > > 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 > > means you can replace \" with " here > Thanks, I haven't paid attention to this detail before. > Best Wishes > > Phillip > Thanks, -- ZheNing Hu
next prev parent reply other threads:[~2021-08-13 8:08 UTC|newest] Thread overview: 32+ 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 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 [this message] 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
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=CAOLTT8QGD08BRuJ5Z8kLdS8gFx+HBeZfsgqotTz0Xch3BNHGPg@mail.gmail.com \ --to=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 v3] [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.