Re: b4 submit ready for beta testing

[Jason Gunthorpe <jgg@ziepe.ca>]

On Wed, Jul 20, 2022 at 04:23:57PM -0700, Linus Torvalds wrote:

> The argument against branch descriptions was always that they didn't
> move around with the branch when you use git pull/push, but for the
> stated use of "branch for sending emailed patches with a cover
> letter", the notion of just having it in the branch description seems
> to be exactly the rigth thing to do.

The thing is not all workflows are "single developer working on their
local machine and then emailing patches". We have "team" workflows
where patches are being shuffled around with push/pull, not email, so
those push/pull problems quickly become relevant. 

Quite often the person who writes the patches and the cover letter is
not the person in the team who is going to git send-email them.

> It also has the advantage that you can edit it at any point, so people
> who don't want to write the cover letter until the very end (as
> somebody piped up in this thread) can continue to do that

If the cover letter is the last commit then 'git commit --amend'
allows editing it as easily as 'git branch --edit description'.

Generally though I think git could use a good built-in tool to edit
commit messages quickly without having to rebase or touch the working
tree.

Jason