mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Jiri Kosina <jkosina@suse.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: fix UTF-8 encoding
Date: Wed, 04 Mar 2015 23:32:09 +0800	[thread overview]
Message-ID: <54F72579.8080903@m4x.org> (raw)
In-Reply-To: <CAMuHMdWhLYzmGPpbJpfF-aNk6QYf1UQb1XVcrfDAO9pUHByZ-Q@mail.gmail.com>

On 03/04/2015 11:21 PM, Geert Uytterhoeven wrote:
> On Wed, Mar 4, 2015 at 4:02 PM, Jiri Kosina <jkosina@suse.cz> wrote:
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -725,7 +725,7 @@ F:        staging/iio/trigger/iio-trig-bfin-timer.c
>>>
>>>  ANDROID DRIVERS
>>>  M:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> -M:   Arve Hj?nnev?g <arve@android.com>
>>> +M:   Arve Hj??nnev??g <arve@android.com>
>>
>> I don't really call that an improvement.
>>
>> The patch was sent as
>>
>>         Content-Type: text/plain; charset=y
>>
>> 'charset=y' (a) doesn't make any sense whatsoever (b) directly contradicts
>> the intent of the patch.
> 
> Just another case of user answering all git questions with "y".
> Been there, done that. Will be handled in git soon
> http://www.spinics.net/lists/git/msg246024.html
> 

Thanks for telling me what I did wrong.  I confirm I did what you
described, I still have the terminal open with the 2 questions git asked me:

$ git send-email --to trivial@kernel.org --cc
linux-kernel@vger.kernel.org 0001-MAINTAINERS-fix-UTF-8-encoding.patch
0001-MAINTAINERS-fix-UTF-8-encoding.patch
The following files are 8bit, but do not declare a
Content-Transfer-Encoding.
    0001-MAINTAINERS-fix-UTF-8-encoding.patch
Which 8bit encoding should I declare [UTF-8]? y
(mbox) Adding cc: Nicolas Iooss <nicolas.iooss_linux@m4x.org> from line
'From: Nicolas Iooss <nicolas.iooss_linux@m4x.org>'
(body) Adding cc: Nicolas Iooss <nicolas.iooss_linux@m4x.org> from line
'Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>'

From: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
To: trivial@kernel.org
Cc: linux-kernel@vger.kernel.org,
	Nicolas Iooss <nicolas.iooss_linux@m4x.org>
Subject: [PATCH] MAINTAINERS: fix UTF-8 encoding
Date: Wed,  4 Mar 2015 22:38:47 +0800
Message-Id: <1425479927-6769-1-git-send-email-nicolas.iooss_linux@m4x.org>
X-Mailer: git-send-email 2.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset=y
Content-Transfer-Encoding: 8bit

Send this email? ([y]es|[n]o|[q]uit|[a]ll): y


It is quite misleading to have both a "non-y" and a "yes/no" answer.
Now that I know this, I will try not to do the same error the next times
I send patches with both UTF-8 and iso-8859-15 characters.

Should I send the patch again with proper encoding?

Nicolas

  reply	other threads:[~2015-03-04 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 14:38 Nicolas Iooss
2015-03-04 15:02 ` Jiri Kosina
2015-03-04 15:21   ` Geert Uytterhoeven
2015-03-04 15:32     ` Nicolas Iooss [this message]
2015-03-04 15:34       ` Jiri Kosina
2015-03-04 15:38         ` Nicolas Iooss

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=54F72579.8080903@m4x.org \
    --to=nicolas.iooss_linux@m4x.org \
    --cc=geert@linux-m68k.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®