Re: [PATCH 10/11] gdb: maintain ptid -> thread map, optimize find_thread_ptid

[Pedro Alves <pedro@palves.net>]

On 2021-07-06 10:31 p.m., Simon Marchi wrote:
>> ( Should this have Co-Authored-By: ? )
> 
> Yes, and probably not just this patch.  I'll go over the series and add
> them where needed.
> 
> When picking up somebody else's patch like this, or the intrusive_list
> patch, is it better to keep the original author as the Author and add
> ourselves with Co-Authored-By, or set the "final" Author as the git
> Author and add previous Authors with Co-Authored-By?

I don't know whether there's an established de facto rule.  I think I'd normally
tend to go more by who's the main author of the change, though that's a
judgement call.  It wouldn't make sense to me to tweak someone else's change
in a minor way, add a couple lines, and then make myself "main git author".
If the workload was more balanced, I'd just keep the original author and add
myself to Co-Authored-By.  E.g., today my version of Luis's tag verification
change, the actual code change I posted was all written by me from scratch, but
the essence of the change isn't that different from Luis's original, so I kept
him as main author.

In this particular thread map patch, I don't even remember who did what in
the patch, I'm fine with how you had it.