Re: [PATCH RFC 11/11] builtin/history: implement "split" subcommand

From: Patrick Steinhardt <ps@pks.im>
Date: Aug 24, 2025, 16:02 UTC
Message-ID: <aKs3qu5W2eqnF1kM@pks.im>
In-Reply-To: <3298210.5fSG56mABF@cayenne>

On Sat, Aug 23, 2025 at 06:37:23PM +0200, Jean-Noël AVILA wrote:

Show 10 quoted lines

> On Tuesday, 19 August 2025 12:56:07 CEST Patrick Steinhardt wrote:
> > @@ -47,6 +48,26 @@ reorder <revision> (--before=<revision>|--
> after=<revision>)::
> >  	commit. The commits must be related to one another and must be
> >  	reachable from the current `HEAD` commit.
> > 
> > +split <revision> [--message=<message>] [--] [<pathspec>...]::
> 
> missing backticks. Also the order of options and <commit> are different from 
> the general synopsis. Is this order allowed?

It is, but this usage definitely wasn't intended. Will fix.

Patrick

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