From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bilbao@vt.edu, bagasdotme@gmail.com, willy@infradead.org,
akiyks@gmail.com, miguel.ojeda.sandonis@gmail.com
Subject: Re: [PATCH v3 0/2] Documentation: Start Spanish translation and include HOWTO
Date: Tue, 01 Nov 2022 16:59:09 -0600 [thread overview]
Message-ID: <87edumxow2.fsf@meer.lwn.net> (raw)
In-Reply-To: <5fd2092e-2f3e-27c0-66a9-94e02efa1e8d@amd.com>
Carlos Bilbao <carlos.bilbao@amd.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@amd.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
next prev parent reply other threads:[~2022-11-01 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 14:55 [PATCH v3 0/2] Documentation: Start Spanish translation and include HOWTO Carlos Bilbao
2022-10-24 14:55 ` [PATCH v3 1/2] Documentation: Start translations to Spanish Carlos Bilbao
2022-10-24 14:55 ` [PATCH v3 2/2] Documentation: Add HOWTO Spanish translation into rst based build system Carlos Bilbao
2022-11-01 21:30 ` [PATCH v3 0/2] Documentation: Start Spanish translation and include HOWTO Jonathan Corbet
2022-11-01 22:33 ` Carlos Bilbao
2022-11-01 22:59 ` Jonathan Corbet [this message]
2022-11-02 9:13 ` Bagas Sanjaya
2022-11-02 10:05 ` Akira Yokosawa
2022-11-02 14:05 ` Jonathan Corbet
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=87edumxow2.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).