Re: b4 submit ready for beta testing

["Michael S. Tsirkin" <mst@redhat.com>]

On Tue, Jul 19, 2022 at 08:44:31AM -0400, James Bottomley wrote:
> It's just really annoying none of our tools supports all workflows: 
> git-format-patch can't work nicely from a tag; the pull workflow seems
> nicest but has no tooling at all around cover letter maintenance and
> the empty commit will be b4 specific.  I think this means there's no
> general agreement on a preferred workflow, which possibly means none is
> deal, but now your tool decides your workflow.

Well the empty commit possibly also with something
special in the subject (e.g. cover! prefix?) sounds like
something that git could learn to support well, no?

Maybe patches in the patchset could gain a prefix too (set! ?)
to make it possible to detect a situation where an unrelated patch
appears in the history after the patchset.

With that I can see some projects actually pushing history like this,
keeping the cover in the tree.

This doesn't require too much work to integrate into git - for starters
just rebase and commit to handle cover letter specially and then git
format-patch to strip the prefix.

-- 
MST