From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>
Subject: Re: [PATCH] devtools: forbid reference to doc.dpdk.org/guides
Date: Wed, 21 Jun 2023 11:51:10 +0100 [thread overview]
Message-ID: <ZJLWHgi0lb6wInDA@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230621080920.861541-1-david.marchand@redhat.com>
On Wed, Jun 21, 2023 at 10:09:20AM +0200, David Marchand wrote:
> Putting links to doc.dpdk.org/guides in our documentation should be
> avoided because it makes the documentation point at the current state of
> the DPDK tree regardless of the version it is generated against.
>
> Note: it should be acceptable to mention previous versions of DPDK (like
> in old release notes), so the pattern has an explicit trailing /.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> devtools/checkpatches.sh | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2023-06-21 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 8:09 David Marchand
2023-06-21 10:51 ` Bruce Richardson [this message]
2023-07-20 4:20 ` 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:
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=ZJLWHgi0lb6wInDA@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).