Re: b4 submit ready for beta testing

[Sudeep Holla <sudeep.holla@arm.com>]

On Tue, Jul 19, 2022 at 02:28:02PM +0200, Geert Uytterhoeven wrote:
> Hi Mark,
> 
> On Tue, Jul 19, 2022 at 2:09 PM Mark Brown <broonie@kernel.org> wrote:
> > On Tue, Jul 19, 2022 at 09:02:40AM +0200, Geert Uytterhoeven wrote:
> > > On Tue, Jul 19, 2022 at 1:10 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> > > > See 'git-tag(1)' "On Re-tagging" for a discussion on why changing tags
> > > > that have been pushed is a bad idea. There are many troublesome
> > > > behaviors here.
> >
> > > > Tags are not a solution to store the cover letter during development..
> >
> > > Oh, I always write my cover letters _after_ development, just before
> > > sending out my series.
> >
> > I tend to find that's less true for followup versions - when revising a
> > series I tend to add to the inter version changelog as I go through
> > making changes.
> 
> You don't add per-patch inter-version changelogs below the "---",
> and collect them all in the cover letter (plus optional rewriting)
> just before sending the new version?
>

I just noticed the same after sending out few fixes[1] using b4 summit.
I didn't use --send directly though as I wanted to add a note in one of the
patch. Also noticed the Subject line broke at the very beginning in 1/3
which git send-email complained and I fixed, not sure if that is an issue
if b4 is used to send email as well.

Sorry for replying here with other comments/feedback as well but the diff
stat missing is main thing and hence I used this thread.

-- 
Regards,
Sudeep

[1] https://lore.kernel.org/all/20220720-arch_topo_fixes-v3-0-43d696288e84@arm.com/