Re: [PATCH 9/8] [DO NOT APPLY, but squash?] git-rebase--interactive: clarify arguments

From: Stefan Beller <sbeller@google.com>
Date: Jan 18, 2018, 21:58 UTC
Message-ID: <CAGZ79kak8u0fuKW5Jg5+hjERCL+RtSCVhMjJz38qQbAG0KKG=w@mail.gmail.com>
In-Reply-To: <nycvar.QRO.7.76.6.1801182233480.31@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>

On Thu, Jan 18, 2018 at 1:36 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> Good idea! I would rather do it as an introductory patch (that only
> converts the existing list).

That makes sense.

Show 7 quoted lines

>
> As to `merge`: it is a bit more complicated ;-)
>
>         m, merge <original-merge-commit> ( <label> | "<label>..." ) [<oneline>]
>                 create a merge commit using the original merge commit's
>                 message (or the oneline, if "-" is given). Use a quoted
>                 list of commits to be merged for octopus merges.

That makes sense. Thanks for being precise at the the user facing UX here.

Thanks, Stefan

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