Skip to content

AUTHORS/mailmap update (with update_authors.pl improvements) #17316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

robn
Copy link
Member

@robn robn commented May 8, 2025

Motivation and Context

Jason: You're not gonna die on the planet, Guy.
Guy: I'm not? Then what's my last name?
Jason: It's, uh, uh - I don't know.
Guy: Nobody knows! Do you know why? Because my character isn't important enough for a last name, because I'm gonna die five minutes in!
Gwen: Guy, you have a last name!
Guy: DO I? DO I? For all you know, I'm "Crewman Number Six"!

– Galaxy Quest, 1999

New contributors, new credits! Hello and welcome!

Description

The important part is the AUTHORS and mailmap updates. Includes @OlCe2's requested update from #17309.

update_authors.pl gets some improvements, to consider Signed-of-by: trailers in name matching, and to output suggestions for mailmap.

How Has This Been Tested?

Run program, tweak, repeat.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

robn added 3 commits May 9, 2025 09:14
I've increasingly found that commits from new contributors have the
author set in the "Github noreply" obfuscated style. If they do have a
better canonical choice, it's usually in the Signed-off-by: trailer in
the commit message.

I had avoided using these in the first version of this program because
they aren't always present, aren't always correct, and some commits have
multiple signoffs. It seems however that requiring either the name or
the email address to match the commit author sufficiently narrows the
scope to be useful for the "Github noreply" situation, which is really
the main sticking point. And of course, if it gets it wrong, overriding
in .mailmap or AUTHORS is always an option.

Sponsored-by: https://despairlabs.com/sponsor/
Signed-off-by: Rob Norris <[email protected]>
Once we've selected a best ident for the AUTHORS file, it makes sense to
set up a corresponding mailmap entry for any other ident for that
committer, to ensure the git history also reflects this into the future.

So, here we output potential mailmap updates for a human to consider.

For the moment, this needs to be done by a human, because update_authors
uses git to get the author names, and thus is reliant on the mailmap
contents to generate its output, so having it update mailmap directly
would introduce a circular dependency that I'm not totally sure about.
It's definitely better than having to go back through the history and
check each commit by hand though.

Sponsored-by: https://despairlabs.com/sponsor/
Signed-off-by: Rob Norris <[email protected]>
Thanks everyone!

Signed-off-by: Rob Norris <[email protected]>
@robn robn changed the title AUTHORS/mailmap update (include update_authors.pl improvements) AUTHORS/mailmap update (with update_authors.pl improvements) May 8, 2025
@amotin amotin added the Status: Code Review Needed Ready for review and testing label May 9, 2025
@tonyhutter
Copy link
Contributor

Thinking long term, it would nice to have the GH runners flag PRs that need to update AUTHORS and .mailmap. That way the PR authors can update them as part of their PRs.

@tonyhutter tonyhutter added Status: Accepted Ready to integrate (reviewed, tested) and removed Status: Code Review Needed Ready for review and testing labels May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants