From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] docs/devel: try and impose some organisation
Date: Fri, 11 Mar 2022 16:29:50 +0100 [thread overview]
Message-ID: <Yitq7nYwYupm9GtV@paraplu> (raw)
In-Reply-To: <20220309135355.4149689-1-alex.bennee@linaro.org>
On Wed, Mar 09, 2022 at 01:53:55PM +0000, Alex Bennée wrote:
> We have a growing set of developer docs but the index is currently in
> order of when stuff was added. Try and make things a bit easier to
> find my adding sub indexes and organising into themes.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> docs/devel/index-api.rst | 15 +++++++++++
> docs/devel/index-build.rst | 20 +++++++++++++++
> docs/devel/index-internals.rst | 22 ++++++++++++++++
> docs/devel/index-process.rst | 18 +++++++++++++
> docs/devel/index-tcg.rst | 17 +++++++++++++
> docs/devel/index.rst | 46 ++++++----------------------------
> 6 files changed, 99 insertions(+), 39 deletions(-)
> create mode 100644 docs/devel/index-api.rst
> create mode 100644 docs/devel/index-build.rst
> create mode 100644 docs/devel/index-internals.rst
> create mode 100644 docs/devel/index-process.rst
> create mode 100644 docs/devel/index-tcg.rst
Yeah, the sub-indexes idea looks good to me. It's good to start this
before it gets out of hand :-)
As discussed on IRC, there seems to be some whitespace damage:
$> git describe
v6.2.0-2381-g034e818c93
$> ~/Mail/patch-temp/cur/1647009097.180136_1.paraplu\:2\,S
Applying: docs/devel: try and impose some organisation
.git/rebase-apply/patch:61: trailing whitespace.
.git/rebase-apply/patch:89: trailing whitespace.
.git/rebase-apply/patch:113: trailing whitespace.
.git/rebase-apply/patch:136: trailing whitespace.
.git/rebase-apply/patch:61: new blank line at EOF.
+
warning: squelched 3 whitespace errors
warning: 8 lines add whitespace errors.
FWIW:
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
[...]
--
/kashyap
prev parent reply other threads:[~2022-03-11 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 13:53 [RFC PATCH] docs/devel: try and impose some organisation Alex Bennée
2022-03-11 15:29 ` Kashyap Chamarthy [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=Yitq7nYwYupm9GtV@paraplu \
--to=kchamart@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.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).