From: Akira Yokosawa <akiyks@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Carlos Bilbao <carlos.bilbao@amd.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bilbao@vt.edu, willy@infradead.org,
miguel.ojeda.sandonis@gmail.com,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v3 0/2] Documentation: Start Spanish translation and include HOWTO
Date: Wed, 2 Nov 2022 19:05:39 +0900 [thread overview]
Message-ID: <b705e85b-c58b-fea4-508f-99ca4bc830b0@gmail.com> (raw)
In-Reply-To: <0d210871-a24a-8e61-b734-ae6df992011d@gmail.com>
On Wed, 2 Nov 2022 16:13:57 +0700, Bagas Sanjaya wrote:
> On 11/2/22 05:59, Jonathan Corbet wrote:
>>
>> 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.
>>
>
> Hi jon,
>
> There is still outstanding issue regarding language identifier slug [1],
> which isn't addressed yet.
>
> [1]: https://lore.kernel.org/linux-doc/48b4a5a1-2a52-4159-699b-9db73a012892@gmail.com/
To be clear, I'm OK with sp_SP/ with the explanation given in the changelog
of v3 1/2.
Regards,
Akira
> [2]: https://lore.kernel.org/linux-doc/Y0ork19pGMhZq8qn@debian.me/
>
> Thanks.
>
next prev parent reply other threads:[~2022-11-02 10:05 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
2022-11-02 9:13 ` Bagas Sanjaya
2022-11-02 10:05 ` Akira Yokosawa [this message]
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=b705e85b-c58b-fea4-508f-99ca4bc830b0@gmail.com \
--to=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--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