From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jeff King <peff@peff.net>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Simon Sandström" <simon@nikanor.nu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Git Mailing List" <git@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Driver Project" <devel@linuxdriverproject.org>
Subject: Re: git email From: parsing (was Re: [GIT PULL] Staging/IIO driver patches for 4.11-rc1)
Date: Fri, 24 Feb 2017 12:03:45 +0100 [thread overview]
Message-ID: <CAMuHMdX+xGUD+K16VCE=ywRgN1Zd4MzSr=NJ=2xz+8e_ixyGKQ@mail.gmail.com> (raw)
In-Reply-To: <20170223061702.bzzgrntotppvwdw6@sigill.intra.peff.net>
On Thu, Feb 23, 2017 at 7:17 AM, Jeff King <peff@peff.net> wrote:
> On Thu, Feb 23, 2017 at 07:04:44AM +0100, Greg KH wrote:
>> > Poor Simon Sandström.
>> >
>> > Funnily enough, this only exists for one commit. You've got several
>> > other commits from Simon that get his name right.
>> >
>> > What happened?
>>
>> I don't know what happened, I used git for this, I don't use quilt for
>> "normal" patches accepted into my trees anymore, only for stable kernel
>> work.
>>
>> So either the mail is malformed, or git couldn't figure it out, I've
>> attached the original message below, and cc:ed the git mailing list.
>>
>> Also, Simon emailed me after this was committed saying something went
>> wrong, but I couldn't go back and rebase my tree. Simon, did you ever
>> figure out if something was odd on your end?
>>
>> Git developers, any ideas?
>
> The problem isn't on the applying end, but rather on the generating end.
> The From header in the attached mbox is:
>
> From: =?us-ascii?B?PT9VVEYtOD9xP1NpbW9uPTIwU2FuZHN0cj1DMz1CNm0/PQ==?= <simon@nikanor.nu>
Slightly related, once in a while I get funny emails through
git-commits-head@vger.kernel.org, where the subject is completely screwed up:
Subject: \x64\x72\x6D\x2F\x74\x69\x6E\x79\x64\x72\x6D\x3A
\x6D\x69\x70\x69\x2D\x64\x62\x69\x3A \x53\x69\x6C\x65\x6E\x63\x65\x3A
‘\x63\x6D\x64’ \x6D\x61\x79 \x62\x65
and some of the mail headers end up in the body as well:
=?UTF-8?Q?\x75\x73\x65\x64_\x75\x6E\x69\x6E\x69\x74\x69\x61\x6C\x69\x7A\x65\x64?=
Return-Path: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Git-Commit: b401f34314db7c60e6d23ee7771cd090b4ef56c1
X-Git-Parent: 1e8ad3d8da4763b238d09244d4d1177aa640c0d3
X-Git-Refname: refs/heads/master
Web:
https://git.kernel.org/torvalds/c/b401f34314db7c60e6d23ee7771cd090b4ef56c1
Commit: b401f34314db7c60e6d23ee7771cd090b4ef56c1
Parent: 1e8ad3d8da4763b238d09244d4d1177aa640c0d3
Refname: refs/heads/master
Author: Noralf Trønnes <noralf@tronnes.org>
AuthorDate: Thu Feb 23 14:29:55 2017 +0100
Committer: Dave Airlie <airlied@redhat.com>
CommitDate: Fri Feb 24 12:08:58 2017 +1000
drm/tinydrm: mipi-dbi: Silence: ‘cmd’ may be used uninitialized
My first guess was Noralf's UTF8 last name, but after looking at a few more,
they all seem to have UTF8 quotes from gcc output in the oneline summary.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-02-24 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 14:56 [GIT PULL] Staging/IIO driver patches for 4.11-rc1 Greg KH
2017-02-22 19:59 ` Linus Torvalds
2017-02-23 6:04 ` git email From: parsing (was Re: [GIT PULL] Staging/IIO driver patches for 4.11-rc1) Greg KH
2017-02-23 6:17 ` Jeff King
2017-02-23 7:59 ` Simon Sandström
2017-02-24 11:03 ` Geert Uytterhoeven [this message]
2017-02-24 18:56 ` Jeff King
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='CAMuHMdX+xGUD+K16VCE=ywRgN1Zd4MzSr=NJ=2xz+8e_ixyGKQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=git@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peff@peff.net \
--cc=simon@nikanor.nu \
--cc=torvalds@linux-foundation.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.