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

Re: What's cooking in git.git (Nov 2021, #07; Mon, 29)

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 6, 2021, 17:50 UTC
Message-ID
<xmqqlf0xhbcc.fsf@gitster.g>
In-Reply-To
<CABPp-BGk9fYqtuYTACmzdXakpV7TP635eqHtHxkoHRT3aa4qFQ@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
> When I first read the documentation, it sounded to me like it was
> implying an abort.  I find 'die' very unnatural as a way to explain
> this behavior; it's too strong of a word.

The way we currently document "git am", we have no word "die" used anywhere in the page. The existing mention of the behaviour are found in these places:

    --continue::
    -r::
    --resolved::
            After a patch failure (e.g. attempting to apply
            conflicting patch), the user has applied it by hand and
            the index file stores the result of the application.
            Make a commit using the authorship and commit log
            extracted from the e-mail message and the current index
            file, and continue.

This uses "failure", and "the user has applied" implies that the user somehow got control back. We give "error:" messages to state that the patch does not apply from apply.c::apply_all_patches() and the caller silently exits, without calling die.

    --show-current-patch[=(diff|raw)]::
            Show the message at which `git am` has stopped due to
            conflicts.  If `raw` is specified, show the raw contents of
            the e-mail message; if `diff`, show the diff portion only.
            Defaults to `raw`.
This uses "has stopped" to describe the same situation.
Show 5 quoted lines
>> (on the other hand, I find 'ask' highly
>> unnatural since we do not ask anything---we just throw the control
>> back the user).
>
> Okay, but what about my previous suggestions of 'stop' or 'interrupt'?

I agree that "stop" would be a good word that is already used to describe "the command cannot make further progress without assistance by the user, so it stops and gives control back".

After that, the user can say "am --skip", "am --abort", or edit plus "am --continue".

Thanks.
Previous: Elijah NewrenNext: Elijah Newren
Message 33 of 42 in “What's cooking in git.git (Nov 2021, #07; Mon, 29)”
  1. Junio C HamanoNov 30, 2021
  2. jk/loosen-urlmatch, was What's cooking in git.git (Nov 2021, #07; Mon, 29)Jeff King, Nov 30, 2021
  3. brian m. carlsonNov 30, 2021
  4. ab/run-command + em/missing-pager (was: What's cooking in git.git (Nov 2021, #07; Mon, 29))Ævar Arnfjörð Bjarmason, Nov 30, 2021
  5. Jeff KingNov 30, 2021
  6. Eric SunshineNov 30, 2021
  7. ab/ci-updates (was: What's cooking in git.git (Nov 2021, #07; Mon, 29))Ævar Arnfjörð Bjarmason, Nov 30, 2021
  8. ab/config-based-hooks-2 (was: What's cooking in git.git (Nov 2021, #07; Mon, 29))Ævar Arnfjörð Bjarmason, Nov 30, 2021
  9. fs/test-prereq (was: What's cooking in git.git (Nov 2021, #07; Mon, 29))Ævar Arnfjörð Bjarmason, Nov 30, 2021
  10. Fabian StelzerDec 1, 2021
  11. jc/c99-var-decl-in-for-loop (was: What's cooking in git.git (Nov 2021, #07; Mon, 29))Ævar Arnfjörð Bjarmason, Nov 30, 2021
  12. ns/tmp-objdir and ns/remerge-diffElijah Newren, Nov 30, 2021
  13. Junio C HamanoDec 3, 2021
  14. Neeraj SinghDec 4, 2021
  15. Elijah NewrenDec 4, 2021
  16. Elijah NewrenNov 30, 2021
  17. Victoria DyeDec 1, 2021
  18. Elijah NewrenNov 30, 2021
  19. Aleen 徐沛文Dec 1, 2021
  20. Elijah NewrenDec 1, 2021
  21. Ævar Arnfjörð BjarmasonDec 3, 2021
  22. Elijah NewrenDec 3, 2021
  23. Ævar Arnfjörð BjarmasonDec 3, 2021
  24. Aleen 徐沛文Dec 6, 2021
  25. Junio C HamanoDec 6, 2021
  26. Aleen 徐沛文Dec 6, 2021
  27. Aleen 徐沛文Dec 6, 2021
  28. Junio C HamanoDec 6, 2021
  29. Aleen 徐沛文Dec 7, 2021
  30. Junio C HamanoDec 7, 2021
  31. Aleen 徐沛文Dec 7, 2021
  32. Elijah NewrenDec 6, 2021
  33. Junio C HamanoDec 6, 2021
  34. en/zdiff3 (was: Re: What's cooking in git.git (Nov 2021, #07; Mon, 29))Elijah Newren, Nov 30, 2021
  35. Junio C HamanoDec 1, 2021
  36. Fabian StelzerDec 1, 2021
  37. Junio C HamanoDec 3, 2021
  38. 0/3 unused-parameter cleanups on top of pw/xdiff-classify-record-in-histogramJeff King, Dec 3, 2021
  39. 1/3 xdiff: drop CMP_ENV macro from xhistogramJeff King, Dec 3, 2021
  40. 2/3 xdiff: drop xpparam_t parameter from histogram cmp_recs()Jeff King, Dec 3, 2021
  41. 3/3 xdiff: drop unused flags parameter from recs_matchJeff King, Dec 3, 2021
  42. Phillip WoodDec 6, 2021

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.