From: Dave Young <dave@youngcopy.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v3 6/7] Added link to Getting Started Guide in index.rst
Date: Tue, 7 Nov 2023 20:47:04 -0500 [thread overview]
Message-ID: <CAMXm8ERy18oN8uUZsQ_bJb+F+V9XZu1wFA7CuJyC3jdG6uRpdg@mail.gmail.com> (raw)
In-Reply-To: <ZUUCEcCpjjKndxgE@bricha3-MOBL.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
I can have it added in patch 1. In the v3 patchset it's added in
0006-Added-link-to-Getting-Started-Guide-in-index.rst.patch
Thanks!
David Young
Professional Copywriter/Technical Writer
Young Copy
+1 (678) 500-9550
https://www.youngcopy.com
On Fri, Nov 3, 2023 at 10:22 AM Bruce Richardson <bruce.richardson@intel.com>
wrote:
> On Fri, Nov 03, 2023 at 12:01:52AM -0400, David Young wrote:
> > ---
> > doc/guides/index.rst | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/doc/guides/index.rst b/doc/guides/index.rst
> > index 244b99624c..51a47d3a51 100644
> > --- a/doc/guides/index.rst
> > +++ b/doc/guides/index.rst
> > @@ -7,6 +7,7 @@ DPDK documentation
> > .. toctree::
> > :maxdepth: 1
> >
> > + getting_started_guide/index
>
> Maybe I am missing something, but what patch is getting_started_guide/index
> added in? Ideally it should be added with just the intro entry in patch 1,
> and then each subsequent patch adds lines to the file as we add sections.
>
> /Bruce
>
[-- Attachment #2: Type: text/html, Size: 1691 bytes --]
next prev parent reply other threads:[~2023-11-08 1:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 4:01 [PATCH v3 0/7] docs: getting started guide consolidation David Young
2023-11-03 4:01 ` [PATCH v3 1/7] Section 1: Introduction David Young
2023-11-03 13:11 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 2/7] Section 2: Install and Build DPDK David Young
2023-11-03 13:55 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 3/7] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-03 14:17 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 4/7] Section 4: Running Applications David Young
2023-11-03 15:13 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 5/7] Section 5: Appendix David Young
2023-11-03 15:23 ` Bruce Richardson
2023-11-16 1:28 ` Dave Young
2023-11-17 13:04 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 6/7] Added link to Getting Started Guide in index.rst David Young
2023-11-03 13:32 ` Bruce Richardson
2023-11-03 14:22 ` Bruce Richardson
2023-11-08 1:47 ` Dave Young [this message]
2023-11-08 2:06 ` Dave Young
2023-11-03 4:01 ` [PATCH v3 7/7] Section 6: Glossary David Young
2023-11-03 15:26 ` Bruce Richardson
2023-11-23 1:26 ` [PATCH v4 0/6] docs: getting started guide consolidation David Young
2023-11-23 1:26 ` [PATCH v4 1/6] Section 1: Introduction David Young
2023-11-23 1:26 ` [PATCH v4 2/6] Section 2: Install and Build DPDK David Young
2023-11-23 1:26 ` [PATCH v4 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-23 1:26 ` [PATCH v4 4/6] Section 4: Running Applications David Young
2023-11-23 1:26 ` [PATCH v4 5/6] Section 5: Appendix David Young
2023-11-23 1:26 ` [PATCH v4 6/6] Section 6: Glossary David Young
2023-12-01 15:17 ` [PATCH v4 0/6] docs: getting started guide consolidation 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=CAMXm8ERy18oN8uUZsQ_bJb+F+V9XZu1wFA7CuJyC3jdG6uRpdg@mail.gmail.com \
--to=dave@youngcopy.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.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 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).