From: Jonathan Corbet <corbet@lwn.net>
To: Rui Li <me@lirui.org>, Alex Shi <alexs@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 0/2] docs/zh_CN: Add userspace-api/index and ebpf Chinese translation
Date: Mon, 17 Oct 2022 08:13:35 -0600 [thread overview]
Message-ID: <87h702fshc.fsf@meer.lwn.net> (raw)
In-Reply-To: <b75832fc-67bb-22b9-39b3-c0816b7ca254@lirui.org>
Rui Li <me@lirui.org> writes:
> So sorry if disturbing. After sending the first patch set, a
> maintainer contacted me and pointed out my email server
> is incorrectly handling DKIM and Message-Id. That causes
> inconvenience for maintainers to review.
>
> I changed my email service and hopefully the DKIM check
> and Message ID won't be wrong. I am not quite sure if I
> should resend or add PATCH v1 version.
>
> Sorry again if I disturbed anyone.
No worries, I was mostly wondering.
As a general rule, whenever you resend a patch series, it is good to add
a note saying why so that others don't have to try to figure it out on
their own.
Thanks,
jon
next prev parent reply other threads:[~2022-10-17 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 13:27 [RESEND PATCH 0/2] docs/zh_CN: Add userspace-api/index and ebpf Chinese translation Rui Li
2022-10-17 13:27 ` [RESEND PATCH 1/2] docs/zh_CN: Add userspace-api/ebpf " Rui Li
2022-10-17 13:27 ` [RESEND PATCH 2/2] docs/zh_CN: Add userspace-api/index " Rui Li
2022-10-17 13:52 ` [RESEND PATCH 0/2] docs/zh_CN: Add userspace-api/index and ebpf " Jonathan Corbet
2022-10-17 14:03 ` Rui Li
2022-10-17 14:13 ` Jonathan Corbet [this message]
2022-10-17 14:17 ` Rui Li
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=87h702fshc.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@lirui.org \
--cc=siyanteng@loongson.cn \
/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).