Lines Matching +full:best +full:- +full:effort

3 # SPDX-License-Identifier: MIT
35 # - a person might change organisations, and so their email address changes
37 # - a person might be paid to work on OpenZFS for their employer, and then hack
41 # - names change for all kinds of reasons
44 # names and emails for a single contributor, and then select the "best" one to
58 # same slug, so at this point we also try to keep the "best" pre-slug value as
59 # the display version. We use this slug to update two maps, one of email->name,
60 # the other of name->email.
68 # Finaly, we consider these groups, and select the "best" name and email for
85 # Storage for the "best looking" version of name or email, keyed on slug.
90 # CONTRIBUTORS: line as-is so we can write it back out to the new file. Then
114 		# The name/email in AUTHORS is already the "best looking"
121 # Next, we load all the commit authors. and form name<->email mappings, keyed
122 # on slug. Note that this format is getting the .mailmap-converted form. This
127 for my $line (reverse qx(git log --pretty=tformat:'%aN:::%aE')) {
138 	# Update the "best looking" display value, but only if we don't already
154 	# it might have been deleted already through a cross-reference
187 	# Decide on the "best" name and email to use
209 # to make upper and lower-case versions of a name or email compare the same,
240 	# For names, "more specific" means "has more non-lower-case characters"
241 	# (in ASCII), guessing that if a person has gone to some effort to
248 	    ($name =~ tr/a-z //) < ($cname =~ tr/a-z //)) {
262 	    ($email =~ tr/a-z //) < ($cemail =~ tr/a-z //)) {
273 		# The "best" name is very subjective, and a simple sort
274 		# produced good-enough results, so I didn't try harder. Use of