Re: b4 submit ready for beta testing

[Jason Gunthorpe <jgg@ziepe.ca>]

On Tue, Jul 19, 2022 at 09:02:40AM +0200, Geert Uytterhoeven wrote:

> > If I use a tag I have to remember to update the tag after every
> > rebase. It is much more likely to break down.
> 
> Why would you have to update the tag? The tag would represent what
> was sent out, i.e. the tag name would include the revision number.
> After rebase, you have to recreate the cover letter (with an
> increased revision number), using the previous tag description as
> a template.

Using a tag as 'what was sent out' might make sense - but that is a
different problem.

In many cases the cover letter is part of the series, and complex
series often have very big cover letters explaining what is going on
that take alot of effort to make and review in a "team based" flow.

Fundamentally, the cover letter needs to be source controlled while it
is being authored just like anything else.

> It would be great if this could auto-insert a lore link to the previous
> revision ("Changes since v${n-1} [https://lore...]").  Git can store
> the commit hash into the Message-Id, but it also contains a timestamp,
> so you can't go easily from tag to Message-Id.

What I've found useful is a tool that automatically generates a git
range-diff between the current branch and the last posted and also
displays the lore link. This helps tremendously producing the change
log.

Jason