Re: b4-0.9.0 available

From: Chuck Lever <chucklever@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	 "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	 Linus Torvalds <torvalds@linuxfoundation.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	 tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4-0.9.0 available
Date: Fri, 24 Jun 2022 13:51:57 -0400	[thread overview]
Message-ID: <CAFMMQGv8E2Bc4bdWG3_eLg5fiHX=gjerQ1s5x1_7f2uo9joZ+w@mail.gmail.com> (raw)
In-Reply-To: <YrXYaE12VFUDucsN@mit.edu>

On Fri, Jun 24, 2022 at 11:30 AM Theodore Ts'o <tytso@mit.edu> wrote:
>
> On Fri, Jun 24, 2022 at 10:51:47AM -0300, Jason Gunthorpe wrote:
> >
> > Unfortunately it is a bit of a PITA for the submitter so not too many
> > people seem to do it.
>
> Yeah, "git notes" in newer versions of git makes it easier to compose
> the cover letter, but tracking the lore URL's of the previous versions
> of the patches that was submitted has to be done completely manually.
> And because it's a PITA, very few people do it.
>
> It would be great if we had some kind of tooling where when someone
> sends a new version of the patch series, the tooling opened an editor
> and allowed the submitted to enter a quick changelog of what changed
> between the v25 and v26 version of the patch, with an option to also
> edit the body of the cover letter.  And then then when the patch is
> sent via e-mail, all of this would be appended to the cummulative
> version of the cover letter.

Interestingly, this kind of per-branch cover letter tracking has also
recently been requested for Stacked Git.

https://github.com/stacked-git/stgit/discussions/186

It would be great if the basic approach could be the same for git,
stgit, and b4.

-- 
"We cannot take our next breath without the exhale."
 -- Ellen Scott Grable