From: Dave Young <dave@youngcopy.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH 0/6] docs: Unify Getting Started Guides
Date: Wed, 11 Oct 2023 14:34:18 -0400 [thread overview]
Message-ID: <CAMXm8ESmA67LXG433DDG_nPjaS6iuEWOvZ5bLQrkHDODAhxqbg@mail.gmail.com> (raw)
In-Reply-To: <c7460baa-9eb5-4891-bc24-45ab94a4aef9@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]
Thank you for reviewing the patches and for your feedback.
1. Regarding the toctree, I've added the new Getting Started Guide so that
it's accessible via the links in the left column. I've tested this on my
local version, and the warning should disappear once the patch is submitted.
2. As for the existing per-platform documentation, it has not been removed
yet because I'm still in the process of developing the consolidated Getting
Started Guide. The existing documentation will remain in place for the time
being.
3. About the context not yet moved from the existing per-platform guides,
I'm considering how best to integrate this information into the new guide.
Bruce, do you have any thoughts on whether these should be kept around for
reference or moved to other files?
I plan to send updated versions of all patches in this series at the same
time, incorporating all the feedback received.
Thank you again for your time and input.
Thanks!
David Young
Professional Copywriter/Technical Writer
Young Copy
+1 (678) 500-9550
https://www.youngcopy.com
On Mon, Sep 25, 2023 at 7:54 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 9/20/2023 4:48 PM, David Young wrote:
> > The separate Getting Started Guides for Linux, FreeBSD, and Windows have
> been
> > consolidated into a single, streamlined guide to simplify the user
> experience
> > and facilitate easier maintenance.
> >
> > David Young (6):
> > Section 1: Introduction
> > Section 2: Install and Build DPDK
> > Section 3: Setting up a System to Run DPDK Applications
> > Section 4: Running Applications
> > Section 5: Appendix
> > Section 6: Glossary
> >
>
> Hi David,
>
> New documentations are not in the toctree, so they are not accessible by
> the links in the left column.
> Sphinx generates warning for this:
> WARNING: document isn't included in any toctree
>
> Also existing per platform documentation is not removed yet.
>
> I assume both above done intentionally for the development phase of this
> documentation, but this is just a reminder in-case not.
>
>
> And not all context seems moved from existing per platform getting
> started guides, is there are plan to keep them around for a while as
> reference, or move that context to other files?
>
>
> Thanks,
> ferruh
>
>
[-- Attachment #2: Type: text/html, Size: 3044 bytes --]
next prev parent reply other threads:[~2023-10-11 18:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:48 David Young
2023-09-20 15:48 ` [PATCH 1/6] Section 1: Introduction David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-10-11 18:26 ` Dave Young
2023-09-20 15:48 ` [PATCH 2/6] Section 2: Install and Build DPDK David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-09-25 12:20 ` Bruce Richardson
2023-09-25 16:05 ` Tyler Retzlaff
2023-10-12 18:08 ` Dave Young
2023-10-17 13:37 ` Tyler Retzlaff
2023-09-20 15:48 ` [PATCH 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-09-25 11:31 ` Ferruh Yigit
2023-09-25 12:22 ` Bruce Richardson
2023-10-12 17:32 ` Dave Young
2023-09-20 15:48 ` [PATCH 4/6] Section 4: Running Applications David Young
2023-09-25 11:32 ` Ferruh Yigit
2023-09-20 15:48 ` [PATCH 5/6] Section 5: Appendix David Young
2023-09-25 11:33 ` Ferruh Yigit
2023-09-25 11:52 ` Ferruh Yigit
2023-09-25 12:24 ` Bruce Richardson
2023-09-20 15:48 ` [PATCH 6/6] Section 6: Glossary David Young
2023-09-25 11:43 ` Ferruh Yigit
2023-09-22 4:15 ` [PATCH 0/6] docs: Unify Getting Started Guides Tyler Retzlaff
2023-09-22 14:47 ` David Marchand
2023-09-22 15:54 ` Bruce Richardson
2023-09-25 11:54 ` Ferruh Yigit
2023-10-11 18:34 ` Dave Young [this message]
2023-10-13 16:28 ` Bruce Richardson
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=CAMXm8ESmA67LXG433DDG_nPjaS6iuEWOvZ5bLQrkHDODAhxqbg@mail.gmail.com \
--to=dave@youngcopy.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).