[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87edumxow2.fsf@meer.lwn.net>
Date: Tue, 01 Nov 2022 16:59:09 -0600
From: Jonathan Corbet <corbet@....net>
To: Carlos Bilbao <carlos.bilbao@....com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
bilbao@...edu, bagasdotme@...il.com, willy@...radead.org,
akiyks@...il.com, miguel.ojeda.sandonis@...il.com
Subject: Re: [PATCH v3 0/2] Documentation: Start Spanish translation and
include HOWTO
Carlos Bilbao <carlos.bilbao@....com> writes:
> On 11/1/22 16:30, Jonathan Corbet wrote:
>
>>
>>
>> I went to apply this series just now, and got the following from "git
>> am":
>>
>> WARNING: Message contains suspicious unicode control characters!
>> Subject: [PATCH v3 2/2] Documentation: Add HOWTO Spanish translation into rst based build system
>> Line: +estable más reciente del kernel, y no están interesados en ayudar a probar
>> ---------------------------------------------------------------^
>> Char: ZERO WIDTH SPACE (0x200b)
>> If you are sure about this, rerun with the right flag to allow.
>>
>> Any idea what the story is there? Could I get a resend without that
>> problem?
> Just tried to apply git am and didn't get any warning. Maybe you are using
> an extra flag? I'm running with git version 2.34.1. Could you try replacing
> the offending char with a space? Hopefully that solves it.
I'm sorry, it was b4 that complained, not git. To see it happen, try:
b4 am 20221024145521.69465-1-carlos.bilbao@....com
There were, in fact, two zero-width spaces in there, and two more in
Junio Hamano's name. I've taken them all out, and learned all about
searching for weird characters in Emacs as a side benefit :)
Series is now applied, thanks.
jon
Powered by blists - more mailing lists