Re: Acked-by: [was: Re: [PATCH v2 1/1] enter.c: Use wmem*() functions with] wide-character strings

On Sun, Feb 15, 2026 at 07:36:45AM +0800, Kevin J. McCarthy wrote:
> On Sat, Feb 14, 2026 at 06:42:28PM +0100, Rene Kita wrote:
> > Sure. I also like getting feedback. I was more wondering if it is worth
> > it that someone has to update the commit message to add the Acked-by or
> > Reviewed-by.
> 
> If we add them to the commit message, who typically does that?  Is it my job
> to track the acks/reviewed-bys, and add them before applying?
> 
> Any tips on workflow?

In the kernel world, we have tools that do this for us, most of us rely
on a tool called `b4` https://b4.docs.kernel.org/en/latest/ but that
might not work for mutt patches given that it relies on lore.kernel.org
to retrieve the patches from and then do the collection of
reviewed/acked tags.

There are some other scripts floating around that other kernel
maintainers use before b4 came to be, personally I just hand-edited the
patches in mutt (using e for edit) to add the tags and then a mutt macro
to automatically apply the patch from the email "|git am -s\n"

hope this helps a bit.

greg k-h