From: Petr Machata <petrm@nvidia.com>
To: 何敏红 <heminhong@kylinos.cn>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Petr Machata <petrm@nvidia.com>, netdev <netdev@vger.kernel.org>
Subject: Re: 回复: Re: 回复: Re: [PATCH] iproute2: prevent memory leak on error return
Date: Wed, 29 Nov 2023 11:35:11 +0100 [thread overview]
Message-ID: <87edg8c04l.fsf@nvidia.com> (raw)
In-Reply-To: <1nkdhqz7po5-1nkg1mm1tbq@nsmail7.0.0--kylin--1>
何敏红 <heminhong@kylinos.cn> writes:
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: base64
[snip]
Let's not have this. The patch that you sent previously was properly
plain text -- can you revert whatever changes you made in the meantime
that make it send HTML mails now?
prev parent reply other threads:[~2023-11-29 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 3:29 回复: Re: 回复: Re: [PATCH] iproute2: prevent memory leak on error return 何敏红
2023-11-29 10:35 ` Petr Machata [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=87edg8c04l.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=heminhong@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.