From: Stephen Hemminger <stephen@networkplumber.org>
To: Nandini Persad <nandinipersad361@gmail.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>, dev@dpdk.org
Subject: Re: [PATCH] doc: reword contributor's guidelines
Date: Tue, 31 Mar 2026 15:32:49 -0700 [thread overview]
Message-ID: <20260331153249.285d7ca9@phoenix.local> (raw)
In-Reply-To: <20250512144842.29976-1-nandinipersad361@gmail.com>
On Mon, 12 May 2025 07:48:41 -0700
Nandini Persad <nandinipersad361@gmail.com> wrote:
> I have revised sections 9-12 for grammar and clarity.
>
> Signed-off-by: Nandini Persad <nandinipersad361@gmail.com>
> ---
> doc/guides/contributing/linux_uapi.rst | 32 ++--
> doc/guides/contributing/patches.rst | 177 +++++++++++-----------
> doc/guides/contributing/stable.rst | 163 ++++++++------------
> doc/guides/contributing/vulnerability.rst | 59 ++++----
> 4 files changed, 193 insertions(+), 238 deletions(-)
These changes were intergrated into: https://patchwork.dpdk.org/project/dpdk/list/?series=37078
prev parent reply other threads:[~2026-03-31 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 14:48 [PATCH] doc: reword contributor's guidelines Nandini Persad
2026-03-31 22:32 ` Stephen Hemminger [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=20260331153249.285d7ca9@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nandinipersad361@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