On Tue, 10 Oct 2023 18:26:35 +0200 Thomas Monjalon <tho...@monjalon.net> wrote:
> 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 <tho...@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:: Acked-by: Stephen Hemminger <step...@networkplumber.org>
