linux-kernel - Re: [PATCH] MAINTAINERS: fix UTF-8 encoding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54F72579.8080903@m4x.org>
Date:	Wed, 04 Mar 2015 23:32:09 +0800
From:	Nicolas Iooss <nicolas.iooss_linux@....org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Jiri Kosina <jkosina@...e.cz>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: fix UTF-8 encoding

On 03/04/2015 11:21 PM, Geert Uytterhoeven wrote:
> On Wed, Mar 4, 2015 at 4:02 PM, Jiri Kosina <jkosina@...e.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@...uxfoundation.org>
>>> -M:   Arve Hj?nnev?g <arve@...roid.com>
>>> +M:   Arve Hj??nnev??g <arve@...roid.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@...nel.org --cc
linux-kernel@...r.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@....org> from line
'From: Nicolas Iooss <nicolas.iooss_linux@....org>'
(body) Adding cc: Nicolas Iooss <nicolas.iooss_linux@....org> from line
'Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@....org>'

From: Nicolas Iooss <nicolas.iooss_linux@....org>
To: trivial@...nel.org
Cc: linux-kernel@...r.kernel.org,
	Nicolas Iooss <nicolas.iooss_linux@....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@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/