From: David Young <dave@youngcopy.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Aaron Conole <aconole@redhat.com>,
David Young <dave@youngcopy.com>
Subject: [PATCH v2 0/3] docs: Unify Getting Started Guides v2 Updates
Date: Tue, 31 Oct 2023 20:49:25 -0400 [thread overview]
Message-ID: <20231101004932.1371-1-dave@youngcopy.com> (raw)
This is version 2 of the patch series for updating the DPDK Documentation.
Thank you to everyone who provided feedback on the first version.
Changes since v1:
- Removed unnecessary verbiage from Section 1: Introduction
- Merged windows_install_build.rst into building_from_sources.rst
- Updated Section 2: Install and Build DPDK based on additional feedback
- Added link in guides/index.rst to Getting Started Guide so now it shows up in menu
The following patches are included in this series:
1/3: GSG Section 1: Introduction - Updated
2/3: Added link to Getting Started Guide in index.rst
3/3: GSG Section 2: Install and Build DPDK - Updated
.../building_from_sources.rst | 124 ++++++++++++++----
.../install_and_build/index.rst | 3 +-
.../windows_install_build.rst | 93 -------------
doc/guides/getting_started_guide/intro.rst | 7 +-
doc/guides/index.rst | 1 +
5 files changed, 99 insertions(+), 129 deletions(-)
delete mode 100644 doc/guides/getting_started_guide/install_and_build/windows_install_build.rst
--
2.41.0.windows.1
next reply other threads:[~2023-11-01 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 0:49 David Young [this message]
2023-11-01 0:49 ` [PATCH 1/3] GSG Section 1: Introduction - Updated based on feedback David Young
2023-11-01 0:49 ` [PATCH 2/3] Added link to Getting Started Guide in index.rst David Young
2023-11-01 0:49 ` [PATCH 3/3] GSG Section 2: Install and Build DPDK - Updated based on feedback David Young
2023-11-02 2:14 ` Tyler Retzlaff
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=20231101004932.1371-1-dave@youngcopy.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).