From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove template comments in old release notes
Date: Fri, 17 Sep 2021 14:53:17 +0200 [thread overview]
Message-ID: <5957949.lEuExA1773@thomas> (raw)
In-Reply-To: <SN6PR11MB30866F70FDFBEFFCB0890DA5FCDD9@SN6PR11MB3086.namprd11.prod.outlook.com>
17/09/2021 12:56, Mcnamara, John:
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, September 15, 2021 5:25 PM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John <john.mcnamara@intel.com>; david.marchand@redhat.com;
> > Yigit, Ferruh <ferruh.yigit@intel.com>
> > Subject: [PATCH] doc: remove template comments in old release notes
> >
> > The release notes comments mention how to generate the documentation
> > with the old & removed build system.
> >
> > Rather than fixing these comments, all old release notes comments
> > are removed, because they are useful only for the current release.
>
>
> Good point. We should remember to remove these how-to comments in the last pass of reviewing the release notes as well.
Yes, basically removing in your patch at the end of a release.
And then add it back for the next release.
prev parent reply other threads:[~2021-09-17 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 16:25 Thomas Monjalon
2021-09-15 16:30 ` Bruce Richardson
2021-09-16 14:27 ` David Marchand
2021-09-23 6:39 ` Thomas Monjalon
2021-09-17 10:56 ` Mcnamara, John
2021-09-17 12:53 ` Thomas Monjalon [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=5957949.lEuExA1773@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@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).