public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 10 Oct 2023 13:52:29 -0600	[thread overview]
Message-ID: <87fs2i5k76.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231010-helping-pajamas-dee038@meerkat>

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

      reply	other threads:[~2023-10-10 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  5:07 [PATCH v3] docs/zh_TW: update contents for zh_TW Hu Haowen
2023-10-10 19:07 ` Jonathan Corbet
2023-10-10 19:35   ` Konstantin Ryabitsev
2023-10-10 19:52     ` Jonathan Corbet [this message]

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=87fs2i5k76.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=src.res.211@gmail.com \
    /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