All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PULL 0/4] Docs patches
Date: Thu, 5 Sep 2019 16:34:33 +0100	[thread overview]
Message-ID: <CAFEAcA8-C4V6EQBZDvLUaL+WoLfnr4wB6tiQNAtH1wN1kRQN3Q@mail.gmail.com> (raw)
In-Reply-To: <20190905134526.32146-1-berrange@redhat.com>

On Thu, 5 Sep 2019 at 14:45, Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> The following changes since commit 500efcfcf0fe2e0dae1d25637a13435ce7b6e421:
>
>   Merge remote-tracking branch 'remotes/rth/tags/pull-or1k-20190904' into staging (2019-09-05 09:33:01 +0100)
>
> are available in the Git repository at:
>
>   https://github.com/berrange/qemu tags/docs-pull-request
>
> for you to fetch changes up to 9f8efa74d3f1cb9ceeee957ee382c2b4feb2ae30:
>
>   docs: split the CODING_STYLE doc into distinct groups (2019-09-05 14:41:00 +0100)
>
> ----------------------------------------------------------------
>
> * Merges HACKING into CODING_STYLE
> * Converts README and CODING_STYLE docs into RST syntax
> * Documents use of auto cleanup functions
>
> ----------------------------------------------------------------
>
> Daniel P. Berrangé (4):
>   docs: convert README, CODING_STYLE and HACKING to RST syntax
>   docs: merge HACKING.rst contents into CODING_STYLE.rst
>   docs: document use of automatic cleanup functions in glib
>   docs: split the CODING_STYLE doc into distinct groups
>
>  CODING_STYLE          | 216 --------------
>  CODING_STYLE.rst      | 641 ++++++++++++++++++++++++++++++++++++++++++
>  HACKING               | 257 -----------------
>  README => README.rst  |  47 ++--
>  scripts/checkpatch.pl |   2 +-

I'm going to apply this, but something I thought of looking at
the diffstat: should some or all of this be in the docs/devel
manual rather than free-floating rst files in the root directory?

thanks
-- PMM


  parent reply	other threads:[~2019-09-05 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 13:45 [Qemu-devel] [PULL 0/4] Docs patches Daniel P. Berrangé
2019-09-05 13:45 ` [Qemu-devel] [PULL 1/4] docs: convert README, CODING_STYLE and HACKING to RST syntax Daniel P. Berrangé
2019-09-05 13:45 ` [Qemu-devel] [PULL 2/4] docs: merge HACKING.rst contents into CODING_STYLE.rst Daniel P. Berrangé
2019-09-05 13:45 ` [Qemu-devel] [PULL 3/4] docs: document use of automatic cleanup functions in glib Daniel P. Berrangé
2019-09-05 13:45 ` [Qemu-devel] [PULL 4/4] docs: split the CODING_STYLE doc into distinct groups Daniel P. Berrangé
2019-09-05 15:34 ` Peter Maydell [this message]
2019-09-06  9:24   ` [Qemu-devel] [PULL 0/4] Docs patches Daniel P. Berrangé
2019-09-06 13:13     ` Eric Blake
2019-09-05 16:08 ` Peter Maydell

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=CAFEAcA8-C4V6EQBZDvLUaL+WoLfnr4wB6tiQNAtH1wN1kRQN3Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.