From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PULL REQUEST] doc: getting started guide for linux.
Date: Thu, 23 Oct 2014 14:51:15 +0200 [thread overview]
Message-ID: <3258807.e10jNUOSjt@xps13> (raw)
In-Reply-To: <1413820404-5877-1-git-send-email-bernard.iremonger@intel.com>
> Bernard Iremonger (1):
> doc: getting started guide for linux
>
> doc/guides/conf.py | 30 +++
> doc/guides/index.rst | 37 +++
> doc/guides/linux_gsg/build_dpdk.rst | 271 +++++++++++++++++++++++
> doc/guides/linux_gsg/build_sample_apps.rst | 234 ++++++++++++++++++++
> doc/guides/linux_gsg/enable_func.rst | 201 +++++++++++++++++
> doc/guides/linux_gsg/index.rst | 86 +++++++
> doc/guides/linux_gsg/intro.rst | 68 ++++++
> doc/guides/linux_gsg/quick_start.rst | 329 ++++++++++++++++++++++++++++
> doc/guides/linux_gsg/sys_reqs.rst | 288 ++++++++++++++++++++++++
It is now pulled in the main repository.
I just removed the whitespaces whose git were complaining about.
Thank you for this nice step done, it's the first document converted into
rst format and merged in the git tree.
It's worth explaining that Bernard is converting all the DPDK guides in
the same way. He's currently working on the documents of version 1.7.
Next step will be to update them for version 1.8.
Then everyone we'll be able to submit some patches for the documentation.
If someone is volunteer to customize appearance of the HTML documents,
he's more than welcome!
Thanks
--
Thomas
prev parent reply other threads:[~2014-10-23 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PULL REQUEST>
2014-10-08 15:12 ` [dpdk-dev] [PULL REQUEST] doc: generate DPDK_Linux_GSG with Sphinx Bernard Iremonger
2014-10-20 15:53 ` [dpdk-dev] [PULL REQUEST] doc: getting started guide for linux Bernard Iremonger
2014-10-23 12:51 ` Thomas Monjalon [this message]
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=3258807.e10jNUOSjt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bernard.iremonger@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).