Skip to content
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

mailmap support #366

Merged
merged 32 commits into from
Mar 29, 2022
Merged

mailmap support #366

merged 32 commits into from
Mar 29, 2022

Conversation

Byron
Copy link
Member

@Byron Byron commented Mar 26, 2022

Take git2's implementation for an idea on how the API could look like.

  • parsing
  • data structure for lookup (see mailmap for prior work
    • make sure this is fast for 400+ entries like in the linux kernel
  • docs
  • gix mailmap verify - check for errors and print them if one comes up.
  • mailmap lookup/creation according to rules in git-repository
  • gix repo mailmap entries - list all entries and inform about errors, too
  • use mailmap in gix t h if present, instead of using own algorithm.

@Byron Byron mentioned this pull request Mar 26, 2022
11 tasks
@Byron Byron changed the title mailmap mailmap support Mar 26, 2022
Byron added 28 commits March 26, 2022 08:32
error handling is tested only by integration-level test,
and more error handling tests would have to be added.
It pulls in a regex engine or parts of it, and for now we avoid that.
That way, one _can_ optimize for performance and be zero copy
after the mail map has been created.
Maybe this can be useful in the estimate-hours program.
Byron added a commit that referenced this pull request Mar 29, 2022
@Byron Byron merged commit d2388d8 into main Mar 29, 2022
@Byron Byron deleted the mailmap branch March 29, 2022 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant