DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [PATCH] doc: remove confusing command to send patch
Date: Tue, 10 Oct 2023 18:26:35 +0200	[thread overview]
Message-ID: <20231010162635.755975-1-thomas@monjalon.net> (raw)

In the contributor guide, it was said that no need to Cc maintainers
for new additions, probably for new directories not having a maintainer.
There is no harm, and it is a good habit, to always Cc maintainers.

Remove this case as it can mislead to not Cc maintainers when needed.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
 doc/guides/contributing/patches.rst | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index e286d9e6d5..d114ceba2b 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -561,10 +561,6 @@ Script ``get-maintainer.sh`` can be used to select maintainers automatically::
   git send-email --to-cmd ./devtools/get-maintainer.sh --cc dev@dpdk.org 000*.patch
-New additions can be sent without a maintainer::
-   git send-email --to dev@dpdk.org 000*.patch
 You can test the emails by sending it to yourself or with the ``--dry-run`` option.
 If the patch is in relation to a previous email thread you can add it to the same thread using the Message ID::

             reply	other threads:[~2023-10-10 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 16:26 Thomas Monjalon [this message]
2023-10-11  2:04 ` fengchengwen
2023-10-11  7:30 ` David Marchand
2023-10-11  8:03   ` Thomas Monjalon
2023-10-11  8:30     ` Bruce Richardson
2023-10-11  8:41       ` Ferruh Yigit
2023-10-11 10:20         ` Thomas Monjalon
2023-10-11 10:22           ` Ferruh Yigit
2023-10-11 16:03             ` Thomas Monjalon
2023-10-11 15:52       ` Stephen Hemminger
2023-10-11 16:02         ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231010162635.755975-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \


* 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).