From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michal Suchanek <hramrach@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Non-ascii mantainers
Date: Mon, 7 Dec 2015 10:18:41 +0100 [thread overview]
Message-ID: <CAMuHMdVxk00fsMLAxQrRF8LMLpiZpAmADgAw6xd-GDzu2LKgZw@mail.gmail.com> (raw)
In-Reply-To: <CAOMqctTiBfxJDvNmC+NnPLpYf4JFcVT0sbWXrkpynhciQFU7Ww@mail.gmail.com>
Hi Michael,
On Tue, Dec 1, 2015 at 6:27 PM, Michal Suchanek <hramrach@gmail.com> wrote:
> On 1 December 2015 at 18:20, Al Viro <viro@zeniv.linux.org.uk> wrote:
>> On Tue, Dec 01, 2015 at 06:10:29PM +0100, Michal Suchanek wrote:
>>> there are non-ascii characters in output of scripts/get_maintainer.pl
>>>
>>> If output of said script is used as --to in git format-patch the patch
>>> is rejected by this list.
>>
>> Try to reproduce that in a UTF8 locale...
>
> I am using UTF-8 locale since ages.
>
> The characters show correctly in my terminal. I have no problem with
> that. The e-mail is then just rejected by the list server.
>
> I don't really care if the maintainers are encoded or whatever.
> However, neither get_maintainers nor git format-patch encodes them and
> the listserver rejects them when not encoded.
I always pass the --to and --cc to git send-email, not to format-patch, and
that works:
git send-email \
--to "Måns Rullgård <mans@mansr.com>" \
--to "David S. Miller <davem@davemloft.net>" \
--cc "netdev@vger.kernel.org" \
--cc "linux-kernel@vger.kernel.org" \
*00*
becomes:
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: =?UTF-8?q?M=C3=A5ns=20Rullg=C3=A5rd?= <mans@mansr.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] ethernet: aurora: AURORA_NB8800 should depend on HAS_DMA
Date: Mon, 7 Dec 2015 10:09:06 +0100
Message-Id: <1449479346-32601-1-git-send-email-geert@linux-m68k.org>
X-Mailer: git-send-email 1.9.1
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:[~2015-12-07 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 17:10 Michal Suchanek
2015-12-01 17:19 ` Joe Perches
2015-12-01 17:20 ` Al Viro
2015-12-01 17:27 ` Michal Suchanek
2015-12-01 20:13 ` Andreas Mohr
2015-12-03 6:55 ` Michal Suchanek
2015-12-07 9:18 ` Geert Uytterhoeven [this message]
2015-12-07 9:40 ` Michal Suchanek
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=CAMuHMdVxk00fsMLAxQrRF8LMLpiZpAmADgAw6xd-GDzu2LKgZw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=hramrach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®