Re: [PATCH v3 15/15] rebase: change the default backend from "am" to "merge"

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 16, 2020, 20:05 UTC
Message-ID: <xmqqwo9rgo9v.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20200116075810.GB242359@google.com>

Jonathan Nieder <jrnieder@gmail.com> writes:

Show 5 quoted lines

> The deployment examples above seem like examples where the user would
> want the script to run on "git am" (and on "git merge --ff-only", for
> that matter) but not on the intermediate commits in "git rebase",
> since when rebasing a multi-commit series, deploying earlier rebased
> commits would cause the deployment to lose the benefit of later fixes.

Agree. The same thing can be said to "git am" accepting a series of multiple patches, though.

$ 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.