[PING][PATCH v5 0/1] update MAINTAINERS file with git trailers

[Guinevere Larsen <blarsen@redhat.com>]

Ping!

There has been some thoughts that this newest direction wasn't the best 
(see Kevin's emails). I would like some more discussion on which 
direction to take the text with regards to approved-by and acked-by 
before sending a new version.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

On 05/10/2023 13:35, Guinevere Larsen wrote:
> Some private chats highlighted that the currently in use git trailers
> aren't explained well enough. This patch aims to fix that by adding the
> information in a more verbose way to guarantee that everyone is on the
> same page about them and refine anything that might still need work.
>
> I forgot that Kevin had given a soft approval of this, so I kept his
> review tag, but further chatter on the latest cauldron conference had
> people agreeing that Acked-by should be used as partial approval, so I
> reworded that section of the patch to be more inline with how other
> projects use it.
>
> One concern that was raised in the conference is how b4 reacts to
> trailing parenthesis. It seems that newer b4 versions (at least on
> 0.12.3) drop that, while older versions (0.10.1) keep it. I'm not sure
> if this change was intentional or not, and I have informed the b4
> project of the regression, but this raises the question: Do we want to
> have the trailing parenthesis saying which areas were approved by an
> ack, or is it ok to just have it in regular text?
>
> Personally I like adding it either way in replies, but not making it a
> requirement when pushing code, so its easy to see in old emails and no
> one gets inconvenienced, but I'm not dead set on this.
>
> Guinevere Larsen (1):
>    [gdb]: add git trailer information on gdb/MAINTAINERS
>
>   gdb/MAINTAINERS | 72 +++++++++++++++++++++++++++++++++++++++++++------
>   1 file changed, 64 insertions(+), 8 deletions(-)
>