From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] doc: add patch submit cheatsheet
Date: Sun, 13 Dec 2015 23:48:29 +0100 [thread overview]
Message-ID: <4613674.jYcSQfm65i@xps13> (raw)
In-Reply-To: <1449682047-30698-1-git-send-email-harry.van.haaren@intel.com>
Hi Harry,
2015-12-09 17:27, Harry van Haaren:
> This patch adds the patch submission cheatsheet to
> the contributers guide. Both HTML and PDF docs show
> the cheatsheet on its own page.
>
> Right clicking the SVG image in the HTML doc allows
> for viewing the image on its own, useful for printing
> in high quality.
>
> The exact appearance of of the cheatsheet will depend
> on the default monospace font installed.
>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
[...]
> doc/guides/contributing/img/patch_cheatsheet.svg | 1484 ++++++++++++++++++++++
> doc/guides/contributing/index.rst | 1 +
> 2 files changed, 1485 insertions(+)
[...]
> --- a/doc/guides/contributing/index.rst
> +++ b/doc/guides/contributing/index.rst
> @@ -9,3 +9,4 @@ Contributor's Guidelines
> design
> versioning
> documentation
> + cheatsheet
>
I think you have missed to add a rst file:
/doc/guides/contributing/index.rst:4: WARNING:
toctree contains reference to nonexisting document 'contributing/cheatsheet'
Should you check the cheatsheet? ;)
next prev parent reply other threads:[~2015-12-13 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 16:23 [PATCH] doc: add patch submit cheatsheet Harry van Haaren
2015-12-09 16:40 ` Thomas Monjalon
2015-12-09 16:47 ` Van Haaren, Harry
2015-12-09 16:51 ` Thomas Monjalon
2015-12-09 16:53 ` Bruce Richardson
2015-12-10 1:37 ` Yuanhan Liu
2015-12-09 17:27 ` [PATCH v2] " Harry van Haaren
2015-12-13 22:48 ` Thomas Monjalon [this message]
2015-12-14 10:03 ` [PATCH v3] " Harry van Haaren
2015-12-14 22:18 ` 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=4613674.jYcSQfm65i@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.