All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, thuth@redhat.com,
	 eblake@redhat.com
Subject: Re: [PATCH v3 0/4] rSTify a few more docs; move them to QEMU Git
Date: Fri, 1 Jul 2022 11:07:38 +0100	[thread overview]
Message-ID: <CAFEAcA9Qqs+zVVvjtuWstfndfU-=xQN_enbWgm2U7Rw4WvuSmg@mail.gmail.com> (raw)
In-Reply-To: <Yr62C1611gbJZshc@pinwheel>

On Fri, 1 Jul 2022 at 09:53, Kashyap Chamarthy <kchamart@redhat.com> wrote:
>
> Ping.
>
> Thomas/Peter: when you get some time, please have a look at this.

I reviewed the one patch that had neither already got an R-by
or some review comments.

thanks
-- PMM


  reply	other threads:[~2022-07-01 10:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 16:43 [PATCH v3 0/4] In v3: Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 1/4] docs: rSTify "security-process" page; move it to QEMU Git Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 2/4] docs: rSTify MailingLists wiki; " Kashyap Chamarthy
2022-06-06 21:53   ` Alistair Francis
2022-06-08  5:46   ` Thomas Huth
2022-06-10 10:23     ` Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 3/4] docs: rSTify GettingStartedDevelopers " Kashyap Chamarthy
2022-07-01 10:06   ` Peter Maydell
2022-06-06 16:43 ` [PATCH v3 4/4] Add a new doc "contacting-the-project.rst" Kashyap Chamarthy
2022-06-08  5:50   ` Thomas Huth
2022-06-06 16:49 ` [PATCH v4 0/4] rSTify a few more docs; move them to QEMU Git [Was: Re: [PATCH v3 0/4] In v3:] Kashyap Chamarthy
2022-06-06 16:55   ` [PATCH v3 0/4] rSTify a few more docs; move them to QEMU Git Kashyap Chamarthy
2022-07-01  8:53     ` Kashyap Chamarthy
2022-07-01 10:07       ` Peter Maydell [this message]
2022-07-04 15:12       ` Thomas Huth

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='CAFEAcA9Qqs+zVVvjtuWstfndfU-=xQN_enbWgm2U7Rw4WvuSmg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=eblake@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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.