git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git cherry-pick conflict error message is deceptive when cherry-picking multiple commits

From
Remi Galan Alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr>
Date
Aug 16, 2016, 08:44 UTC
Message-ID
<968827697.1226723.1471337060482.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To
<09d485df-7d14-97f8-9db9-e3db7512bd68@nokia.com>
Hi Stephen,
Stephen Morton <stephen.morton@nokia.com> writes:
Show 14 quoted lines
> +                        if  (multiple_commits)
> +                               advise(_("after resolving the conflicts,
> mark the corrected paths with 'git add <paths>' or 'git rm <paths>'\n"
> +                                        "then continue with 'git %s
> --continue'\n"
> +                                        "or cancel with 'git %s
> --abort'" ), action_name(opts), action_name(opts));
> +                        else
> +                                advise(_("after resolving the
> conflicts, mark the corrected paths\n"
> +                                        "with 'git add <paths>' or 'git
> rm <paths>'\n"
> +                                        "and commit the result with
> 'git commit'"));

In both cases (multiple_commits or not), the beginning of the advise is nearly the same, with only a '\n' in the middle being the difference:

multiple_commits:
 "after resolving the conflicts, mark the corrected paths with 'git
 add <paths>' or 'git rm <paths>'\n"
!multiple_commits:
 "after resolving the conflicts, mark the corrected paths\n with 'git
 add <paths>' or 'git rm <paths>'\n"
                                                  ~~~~~~~^

In 'multiple_commits' case the advise is more than 80 characters long, did you forget the '\n' in that case?

If you end up using the same beginning of advice, maybe it's possible to give it before the 'if(multiple_commits)' and avoid duplication of the lines.

Thanks, Rémi

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 8 in “Re: git cherry-pick conflict error message is deceptive when cherry-picking multiple commits”
  1. Stephen MortonAug 10, 2016
  2. Christian CouderAug 14, 2016
  3. Stephen MortonAug 17, 2016
  4. Remi Galan AlfonsoAug 17, 2016
  5. Junio C HamanoAug 17, 2016
  6. Johannes SchindelinAug 18, 2016
  7. Remi Galan AlfonsoAug 16, 2016
  8. Johannes SchindelinAug 17, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.