From: Thomas Huth <thuth@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH 0/6] trivial-patches for 2023-07-16
Date: Mon, 24 Jul 2023 09:23:30 +0200 [thread overview]
Message-ID: <57bab3e4-f7bb-de3d-d651-46c9d1cc6ea2@redhat.com> (raw)
In-Reply-To: <02d123c8-92c6-c7e2-02df-d9ed9d9ba980@tls.msk.ru>
On 16/07/2023 14.05, Michael Tokarev wrote:
> 16.07.2023 14:57, Michael Tokarev пишет:
>> The following changes since commit 7d07a21ec003724475566073404c5893e36de5e5:
>>
>> tree-wide spelling fixes in comments and some messages: hw/9pfs
>> (2023-07-16 13:59:17 +0300)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.com/mjt0k/qemu.git/ tags/trivial-patches-pull
>>
>> for you to fetch changes up to 7d07a21ec003724475566073404c5893e36de5e5:
>>
>> tree-wide spelling fixes in comments and some messages: hw/9pfs
>> (2023-07-16 13:59:17 +0300)
>>
>> ----------------------------------------------------------------
>> trivial-patches for 2023-07-16
>>
>> This contains a doc fix for riscv and reviewed spelling fixes.
>> ----------------------------------------------------------------
>
> This meant to be a PULL request, not PATCH series.. :)
I guess you have to resend with a PULL in the subject?
Thomas
next prev parent reply other threads:[~2023-07-24 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 11:57 [PATCH 0/6] trivial-patches for 2023-07-16 Michael Tokarev
2023-07-16 11:57 ` [PATCH 1/6] docs/system/target-riscv.rst: tidy CPU firmware section Michael Tokarev
2023-07-16 11:57 ` [PATCH 2/6] tree-wide spelling fixes in comments and some messages: migration/ Michael Tokarev
2023-07-16 11:57 ` [PATCH 3/6] tree-wide spelling fixes in comments and some messages: s390x Michael Tokarev
2023-07-16 11:57 ` [PATCH 4/6] tree-wide spelling fixes in comments and some messages: arm Michael Tokarev
2023-07-16 11:58 ` [PATCH 5/6] tree-wide spelling fixes in comments and some messages: other architectures Michael Tokarev
2023-07-16 11:58 ` [PATCH 6/6] tree-wide spelling fixes in comments and some messages: hw/9pfs Michael Tokarev
2023-07-16 12:05 ` [PATCH 0/6] trivial-patches for 2023-07-16 Michael Tokarev
2023-07-24 7:23 ` Thomas Huth [this message]
2023-07-16 15:58 ` Philippe Mathieu-Daudé
2023-07-17 9:49 ` Michael Tokarev
2023-07-24 9:06 ` 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=57bab3e4-f7bb-de3d-d651-46c9d1cc6ea2@redhat.com \
--to=thuth@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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).