Gerald Pfeifer <ger...@pfeifer.com> writes: > On Wed, 3 Jul 2024, Sam James wrote: >>> Now, a bigger question: Why would anyone need to know my gcc.gnu.org >>> username (or e-mail address) in the Bugzilla context? >> Isn't it answered in the original proposal? It makes CCing the committer >> of a bisect result way easier. > > No, it's not. And no, it does not in my case, for example. > > Hence my counter proposal (with emphasis added): > > A counter proposal for the original request would be an OPTIONAL field > to include in case the e-mail address listed in the MAINTAINERS file > does NOT serve as the Bugzilla account.
I don't think this helps the usecase I mentioned though. There are a bunch of developers who have a blank or unrelated "real name" on Bugzilla, so you can't go from a committing email -> Bugzilla account easily. If every developer has to use @gcc.gnu.org on Bugzilla, and we normalise on @gcc.gnu.org, things become easier to map. So, for example with your counter proposal, this doesn't aid me if someone committed with a third email they use for commits/authorship, as MAINTAINERS won't provide any information in mapping it to a Bugzilla account (as I have no idea what to lookup).
