All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Peter Chubb" <peter.chubb@nicta.com.au>,
	"Andreas Färber" <andreas.faerber@web.de>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Jason Wang" <jasowang@redhat.com>,
	"Aaron Larson" <alarson@ddci.com>
Subject: Re: [RFC PATCH] mailmap/gitdm: more fixes for bad tags and authors
Date: Tue, 15 Mar 2022 09:43:45 +1100	[thread overview]
Message-ID: <87a6ds40ke.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220311135200.680127-1-alex.bennee@linaro.org>

Alex Bennée <alex.bennee@linaro.org> writes:
> I was running some historical tags for the last 10 years and got the
> following warnings:
>
>   git log --use-mailmap --numstat --since "June 2010" | ~/src/gitdm.git/gitdm -n -l 5
>   alarson@ddci.com is an author name, probably not what you want
>   bad utf-8 ('utf-8' codec can't decode byte 0xe4 in position 552: invalid continuation byte) in patchm skipping
>   bad utf-8 ('utf-8' codec can't decode byte 0xe4 in position 342: invalid continuation byte) in patchm skipping
>   michael@ozlabs.org  is an author name, probably not what you want
>   Oops...funky email nicta.com.au
>   bad utf-8 ('utf-8' codec can't decode byte 0xe9 in position 232: invalid continuation byte) in patchm skipping
>   Oops...funky email andreas.faerber
>   Grabbing changesets...done
>   Processed 76422 csets from 1902 developers
>
> The following fixes try and alleviate that although I still get a
> warning for Aaron which I think is from 9743cd5736.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Aaron Larson <alarson@ddci.com>
> Cc: Andreas Färber <andreas.faerber@web.de>
> Cc: Jason Wang <jasowang@redhat.com>
> Cc: Michael Ellerman <michael@ellerman.id.au>
> Cc: Peter Chubb <peter.chubb@nicta.com.au>
> ---
>  .mailmap              | 6 ++++++
>  contrib/gitdm/aliases | 5 ++++-
>  2 files changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/.mailmap b/.mailmap
> index 5113f55b3a..5dc168b199 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -28,7 +28,11 @@ Thiemo Seufer <ths@networkno.de> ths <ths@c046a42c-6fe2-441c-8c8c-71466251a162>
>  malc <av1474@comtv.ru> malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162>
>  
>  # Corrupted Author fields
> +Aaron Larson <alarson@ddci.com> alarson@ddci.com
> +Andreas Färber <andreas.faerber@web.de> Andreas Färber <andreas.faerber>
> +Jason Wang <jasowang@redhat.com> Jason Wang <jasowang>
>  Marek Dolata <mkdolata@us.ibm.com> mkdolata@us.ibm.com <mkdolata@us.ibm.com>
> +Michael Ellerman <michael@ellerman.id.au> michael@ozlabs.org <michael@ozlabs.org>

I prefer to use mpe@ellerman.id.au for coding related things, but
obviously this address also works.

cheers


  parent reply	other threads:[~2022-03-14 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 13:52 [RFC PATCH] mailmap/gitdm: more fixes for bad tags and authors Alex Bennée
2022-03-13 13:59 ` Philippe Mathieu-Daudé
2022-03-14 22:43 ` Michael Ellerman [this message]
2022-03-14 23:20   ` alarson
2022-03-15  8:38     ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6ds40ke.fsf@mpe.ellerman.id.au \
    --to=michael@ellerman.id.au \
    --cc=alarson@ddci.com \
    --cc=alex.bennee@linaro.org \
    --cc=andreas.faerber@web.de \
    --cc=jasowang@redhat.com \
    --cc=peter.chubb@nicta.com.au \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.