DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Laatz <kevin.laatz@intel.com>
To: Robin Jarry <robin.jarry@6wind.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Zhihong Wang <zhihong.wang@intel.com>,
	Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>,
	Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove references to python 2
Date: Fri, 2 Oct 2020 17:04:23 +0100	[thread overview]
Message-ID: <52a527ab-063e-d5d3-e782-f500a4794aa9@intel.com> (raw)
In-Reply-To: <20201002154753.1015-1-robin.jarry@6wind.com>

On 02/10/2020 16:47, Robin Jarry wrote:
> Python 2 support has now been dropped. Remove references to it in the
> documentation.
>
> Since all python scripts now have a proper shebang that calls python3,
> execute the scripts directly without specifying the interpreter.
>
> Sphinx version from most Linux distros is OK in 2020, do not encourage
> people to break their system by installing with pip. Use the distros
> official packages.
>
> Signed-off-by: Robin Jarry <robin.jarry@6wind.com>
> ---
>   doc/guides/conf.py                        | 2 +-
>   doc/guides/contributing/documentation.rst | 8 ++------
>   doc/guides/howto/telemetry.rst            | 2 +-
>   doc/guides/nics/virtio.rst                | 4 ++--
>   doc/guides/rel_notes/deprecation.rst      | 4 ++--
>   doc/guides/tools/testbbdev.rst            | 2 +-
>   6 files changed, 9 insertions(+), 13 deletions(-)
>
Acked-by: Kevin Laatz <kevin.laatz@intel.com>

  parent reply	other threads:[~2020-10-02 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 15:47 Robin Jarry
2020-10-02 15:52 ` Bruce Richardson
2020-10-02 15:55   ` Robin Jarry
2020-10-02 16:05     ` Bruce Richardson
2020-10-02 16:04 ` Kevin Laatz [this message]
2020-10-05  8:23 ` David Marchand

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=52a527ab-063e-d5d3-e782-f500a4794aa9@intel.com \
    --to=kevin.laatz@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    --cc=nhorman@tuxdriver.com \
    --cc=nicolas.chautru@intel.com \
    --cc=robin.jarry@6wind.com \
    --cc=zhihong.wang@intel.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;
as well as URLs for NNTP newsgroup(s).