All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, stefanha@redhat.com,
	peter.maydell@linaro.org, agraf@csgraf.de
Subject: Re: [RFC PATCH  3/4] docs/devel: simplify the minimal checklist
Date: Wed, 12 Oct 2022 13:14:17 +0100	[thread overview]
Message-ID: <Y0avmWEScsC57zBt@redhat.com> (raw)
In-Reply-To: <20221012121152.1179051-4-alex.bennee@linaro.org>

On Wed, Oct 12, 2022 at 01:11:51PM +0100, Alex Bennée wrote:
> The bullet points are quite long and contain process tips. Move those
> bits of the bullet to the relevant sections and link to them. Use a
> table for nicer formatting of the checklist.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
>  docs/devel/submitting-a-patch.rst | 75 ++++++++++++++++++++-----------
>  roms/qboot                        |  2 +-

git submodule surprise !


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2022-10-12 12:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 12:11 [RFC PATCH 0/4] docs/devel suggestions for discussion Alex Bennée
2022-10-12 12:11 ` [RFC PATCH 1/4] docs/devel: add a maintainers section to development process Alex Bennée
2022-10-12 14:59   ` Stefan Hajnoczi
2022-10-13  8:39   ` Markus Armbruster
2022-10-14  9:26   ` Mark Cave-Ayland
2022-10-14 11:23     ` Markus Armbruster
2022-10-14 13:24       ` Alex Bennée
2022-10-20 10:51         ` Peter Maydell
2022-10-12 12:11 ` [RFC PATCH 2/4] docs/devel: make language a little less code centric Alex Bennée
2022-10-12 15:53   ` Paolo Bonzini
2022-10-12 12:11 ` [RFC PATCH 3/4] docs/devel: simplify the minimal checklist Alex Bennée
2022-10-12 12:14   ` Daniel P. Berrangé [this message]
2022-10-12 15:02   ` Stefan Hajnoczi
2022-10-14  9:31   ` Mark Cave-Ayland
2022-10-12 12:11 ` [RFC PATCH 4/4] docs/devel: try and improve the language around patch review Alex Bennée
2022-10-13  8:40   ` Markus Armbruster
2022-10-12 15:02 ` [RFC PATCH 0/4] docs/devel suggestions for discussion Stefan Hajnoczi
2022-10-12 15:56 ` Paolo Bonzini
2022-10-14  9:46 ` Mark Cave-Ayland
2022-10-14 11:35   ` Markus Armbruster
2022-10-14 13:31     ` Alex Bennée

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=Y0avmWEScsC57zBt@redhat.com \
    --to=berrange@redhat.com \
    --cc=agraf@csgraf.de \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.