Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
From:   Jonathan Corbet <corbet@lwn.net>
To:     Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc:     Hu Haowen <src.res.211@gmail.com>, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs/zh_TW: update contents for zh_TW
In-Reply-To: <20231010-helping-pajamas-dee038@meerkat>
References: <20231010050727.49212-1-src.res.211@gmail.com>
 <87a5sq70uy.fsf@meer.lwn.net> <20231010-helping-pajamas-dee038@meerkat>
Date:   Tue, 10 Oct 2023 13:52:29 -0600
Message-ID: <87fs2i5k76.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

>> Putting your patches inline would be the right thing to do in any case.
>
> I'm not sure if your client is showing it differently, but to me the patch
> appears to be just like any other -- it's inline and properly formed.

OK, weird...looking at the raw message it's definitely inline; no idea
why notmuch is showing it as an attachment.

>> Rather than force another round, I've tried to the patch directly (but
>> see below), but it would be good to figure out why lore doesn't like it.
>> Konstantin, any ideas?
>
> If you like, we can migrate linux-doc to the new infrastructure and then you
> will probably see it on lore faster than it's delivered into your inbox. :)

Sure, I'd be happy to see it move anytime.

Thanks,

jon