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

Re: [PATCH v2] status: suggest `git merge --continue`, not `git commit`

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 9, 2026, 14:28 UTC
Message-ID
<3e26cf00-ce81-486a-a6a6-720d22b8f118@app.fastmail.com>
In-Reply-To
<pull.2249.v2.git.1791551486318.gitgitgadget@gmail.com>
On Fri, Oct 9, 2026, at 15:11, Julia Evans via GitGitGadget wrote:
Show 14 quoted lines
> From: Julia Evans <julia@jvns.ca>
>
> During a merge conflict, we suggest using --continue to continue the
> merge for rebase, revert, and cherry-pick.
>
> Change the `git merge` advice to be consistent.
> Commit 367ff694281ce569edd8f6e444fc770f92f5d215 says that
>[snip]
> Signed-off-by: Julia Evans <julia@jvns.ca>
>[snip]
>     Changes in v2:
>
>      * Use git show -s --format=reference to format the reference in the
>        commit message (thanks to Phillip)
But this isn’t changed?

You can use this `commit --amend` snippet to change it. It worked for me at least.

    cat >rewrite-msg.sh <<-\EOF
    #!/bin/sh
    file="$1"
    git format-rev --stdin-mode=text --format=reference <"$file" \
        | par g0 \
        | sponge "$file"
    EOF
    chmod +x rewrite-msg.sh
    GIT_EDITOR=./rewrite-msg.sh git commit --amend
>      * change to "conclude the merge" (thanks to Phillip)
>
>[snip]
Previous: Julia Evans via GitGitGadgetNext: Julia Evans
Message 7 of 11 in “status: suggest `git merge --continue`, not `git commit`”
  1. status: suggest `git merge --continue`, not `git commit`Julia Evans via GitGitGadget, Oct 6, 2026
  2. Phillip WoodOct 6, 2026
  3. Julia EvansOct 9, 2026
  4. Junio C HamanoOct 6, 2026
  5. Julia EvansOct 9, 2026
  6. status: suggest `git merge --continue`, not `git commit`Julia Evans via GitGitGadget, Oct 9, 2026
  7. Kristoffer HaugsbakkOct 9, 2026
  8. Julia EvansOct 9, 2026
  9. status: suggest `git merge --continue`, not `git commit`Julia Evans via GitGitGadget, Oct 9, 2026
  10. Phillip WoodOct 9, 2026
  11. Junio C HamanoOct 9, 2026

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.