From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] version: 19.11-rc0
Date: Tue, 13 Aug 2019 10:53:02 +0200 [thread overview]
Message-ID: <3633614.CjKecApOvI@xps> (raw)
In-Reply-To: <CAJFAV8yUKSAkkf-9T2cHH7xUL3E_NksOx6bOBC48vsoY-QxmHw@mail.gmail.com>
13/08/2019 09:46, David Marchand:
> On Tue, Aug 13, 2019 at 1:17 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 12/08/2019 13:43, David Marchand:
> > > Start a new release cycle with empty release notes.
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > > ---
> > > VERSION | 2 +-
> > > doc/guides/rel_notes/release_19_11.rst | 214 +++++++++++++++++++++++++++++++++
> >
> > doc/guides/rel_notes/release_19_11.rst: WARNING: document isn't included in any toctree
>
> Indeed, trusted your patch on 19.05-rc0 and the CI did not report any
> error (normal when it does not actually build the doc ;-)).
Don't trust anyone ;)
> I will send a fix for the CI and respin.
>
>
> > 1/ the new file must be linked in doc/guides/rel_notes/index.rst
> >
> > Please compare with the latest release notes, I see two more misses:
> > 2/ .. include:: <isonum.txt>
>
> It is unused at this point.
> Do you want to include it in prevision of future changes?
I think it is good to have, so we can use |reg| or other signs
without wondering why it does not work.
I remember Bruce wanted to have it.
> > 3/ increased lib versions
>
> I'll check.
Thanks
next prev parent reply other threads:[~2019-08-13 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 11:43 [dpdk-dev] [PATCH] version: 19.11-rc0 David Marchand
2019-08-12 23:17 ` Thomas Monjalon
2019-08-13 7:46 ` David Marchand
2019-08-13 8:53 ` Thomas Monjalon [this message]
2019-08-13 12:18 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-08-13 12:58 ` 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=3633614.CjKecApOvI@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.