From: Muhammad Bilal <m.bilal@emumba.com>
To: Luca Boccassi <bluca@debian.org>
Cc: thomas@monjalon.net, john.mcnamara@intel.com, dev@dpdk.org,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 18.11 17.11] doc: in doc-clean removed the folder not containing rst files
Date: Fri, 20 Mar 2020 14:53:51 +0500 [thread overview]
Message-ID: <CAOFC0T201ZGydo9yC-nyrKG=cxcQGYKxuaAdqq1z1EoO983RLg@mail.gmail.com> (raw)
In-Reply-To: <aba60e36f058b6b284c53570114b5c083d2ed625.camel@debian.org>
On Fri, Mar 20, 2020 at 2:39 PM Luca Boccassi <bluca@debian.org> wrote:
>
> On Fri, 2020-03-20 at 13:02 +0500, Muhammad Bilal wrote:
> > in doc-clean removing the folder which contain
> > the text files and no .rst files,
> > they cause problem When switching branches and compiling
> > the documentation for older releases (for example
> > building a documentation on 18.11 or 17.11, with a
> > documentation on master branch, built before.
> >
> > Bugzilla ID: 364
> > Cc: Thomas Monjalon <thomas@monjalon.net>
> > Cc: John McNamara <john.mcnamara@intel.com>
> > Cc: M: Luca Boccassi <bluca@debian.org>
> > Cc: dev@dpdk.org
> > Cc: stable@dpdk.org
> > Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
> > ---
> > v2:
> > * Added Details of branches for which patch is used.
> > * This patch is intended for v18.11 and v17.11 branches
>
> Thanks for the patch, but 17.11 is EOL and will no longer receive
> updates.
>
This bug also occurs on 18.11
So this patch is also valid for 18.11.
> --
> Kind regards,
> Muhammad Bilal
next prev parent reply other threads:[~2020-03-20 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200319132722.11325-1-m.bilal@emumba.com>
2020-03-20 8:02 ` Muhammad Bilal
2020-03-20 9:39 ` Luca Boccassi
2020-03-20 9:53 ` Muhammad Bilal [this message]
2020-03-20 10:02 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2020-03-24 7:04 ` Muhammad Bilal
2020-03-24 12:57 ` Kevin Traynor
2020-04-15 16:51 ` Kevin Traynor
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='CAOFC0T201ZGydo9yC-nyrKG=cxcQGYKxuaAdqq1z1EoO983RLg@mail.gmail.com' \
--to=m.bilal@emumba.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=stable@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).