Re: storing cover letter of a patch series?

From: Martin Fick <mfick@codeaurora.org>
Date: Aug 5, 2016, 21:20 UTC
Message-ID: <10752620.2J2dEZLIGc@mfick1-lnx>
In-Reply-To: <xmqqy44bxm0h.fsf@gitster.mtv.corp.google.com>

On Friday, August 05, 2016 08:39:58 AM you wrote:

Show 7 quoted lines

>  * A new topic, when you merge it to the "lit" branch, you
> describe the cover as the merge commit message.
> 
>  * When you updated an existing topic, you tell a tool
> like "rebase -i -p" to recreate "lit" branch on top of
> the mainline.  This would give you an opportunity to
> update the cover.

This is a neat idea. How would this work if there is no merge commit (mainline hasn't moved)?

-Martin

-- 
The Qualcomm Innovation Center, Inc. is a member of Code 
Aurora Forum, hosted by The Linux Foundation

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