Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 13, 2017, 00:30 UTC
Message-ID: <xmqq60bjyjna.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <alpine.DEB.2.21.1.1710122110170.40514@virtualbox>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> (The funny "squash!" followed by a complete version of the
>> rewritten commit message is what I do until I -- or anybody else
>> -- comes up with a patch to implement support for "reword!".)

I have wished for something like that for a long time; it has been (and it still is) a bit unclear what the semantics and UI should look like, but still, such a feature would be quite useful.

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