qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Michael Ellerman" <michael@ellerman.id.au>,
	"Jason Wang" <jasowang@redhat.com>,
	"Peter Chubb" <peter.chubb@nicta.com.au>,
	"Andreas Färber" <andreas.faerber@web.de>,
	"Aaron Larson" <alarson@ddci.com>
Subject: Re: [RFC PATCH] mailmap/gitdm: more fixes for bad tags and authors
Date: Sun, 13 Mar 2022 14:59:29 +0100	[thread overview]
Message-ID: <bf77a623-3915-d3bc-2837-998ecb636a65@gmail.com> (raw)
In-Reply-To: <20220311135200.680127-1-alex.bennee@linaro.org>

On 11/3/22 14:52, Alex Bennée wrote:
> 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/contrib/gitdm/aliases b/contrib/gitdm/aliases
> index 4792413ce7..5b31635c15 100644
> --- a/contrib/gitdm/aliases
> +++ b/contrib/gitdm/aliases
> @@ -34,8 +34,11 @@ malc@c046a42c-6fe2-441c-8c8c-71466251a162 av1474@comtv.ru
>   # canonical emails
>   liq3ea@163.com liq3ea@gmail.com
>   
> -# some broken tags
> +# some broken DCO tags

> +alarson@ddci.com alarson@ddci.com

Is this one useful? Otherwise:
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>


  reply	other threads:[~2022-03-13 14:00 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é [this message]
2022-03-14 22:43 ` Michael Ellerman
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=bf77a623-3915-d3bc-2837-998ecb636a65@gmail.com \
    --to=philippe.mathieu.daude@gmail.com \
    --cc=alarson@ddci.com \
    --cc=alex.bennee@linaro.org \
    --cc=andreas.faerber@web.de \
    --cc=jasowang@redhat.com \
    --cc=michael@ellerman.id.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).