From: Kevin Traynor <ktraynor@redhat.com>
To: Muhammad Bilal <m.bilal@emumba.com>,
john.mcnamara@intel.com,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: Luca Boccassi <bluca@debian.org>,
thomas@monjalon.net, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2 18.11 17.11] doc: in doc-clean removed the folder not containing rst files
Date: Tue, 24 Mar 2020 12:57:47 +0000 [thread overview]
Message-ID: <ead08321-7d57-2f51-d945-dd5af0fe692f@redhat.com> (raw)
In-Reply-To: <CAOFC0T2he+S1Ct5G01C5eKyHD+yGK=EPF1NVvOtKOjAGg71nrg@mail.gmail.com>
On 24/03/2020 07:04, Muhammad Bilal wrote:
> On Fri, Mar 20, 2020 at 3:02 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>>
>> On 20/03/2020 09:53, Muhammad Bilal wrote:
>>> 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.
>>
>> No, This patch is not for dpdk master, it is intended only for 18.11 branch
>> when we switch to 18.11 branch (after making documentation in master or newer branch ) an error occurs in making documentation on 18.11 branch.
>> So This patch is intended to solve this problem.
The line to remove the search dir from commit [1] fixes the api build
for me.
My pdf build is not working atm and I'm not sure about the paths. Can
doc maintainers review this please.
[1]
commit 92d6c874d33dbbd3ace7c06a3490a61ff6641d61
Author: Aideen McLoughlin <aideen.mcloughlin@intel.com>
Date: Thu Jun 27 14:58:19 2019 +0100
doc: add search engine for API
>>>> --
>>>> Kind regards,
>>>> Muhammad Bilal
>>>
>>
>
next prev parent reply other threads:[~2020-03-24 12:58 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 ` [dpdk-dev] " Muhammad Bilal
2020-03-20 9:39 ` Luca Boccassi
2020-03-20 9:53 ` Muhammad Bilal
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 [this message]
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=ead08321-7d57-2f51-d945-dd5af0fe692f@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=m.bilal@emumba.com \
--cc=marko.kovacevic@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).