Re: [PATCH v4 0/2] history: sign rewritten commits

From: Souma <git@5ouma.me>
Date: Oct 3, 2026, 13:38 UTC
Message-ID: <2ddd0d1c-82e8-4793-b109-6c37a88bda23@app.fastmail.com>
In-Reply-To: <xmqq7bjzvhxq.fsf@gitster.g>

Yes, this is expected. The output is an internal completion protocol with options before  --  and generated negated options after it. Other similar commands, such as git rebase and git commit, use the same parse-options behavior and produce the same pattern.

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