From: Thomas Huth <thuth@redhat.com>
To: Richard Zak <richard.j.zak@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] Fix for Haiku
Date: Sun, 4 Jul 2021 20:34:38 +0200 [thread overview]
Message-ID: <020c0056-deb1-9f2b-29a4-a3c8a7ac266f@redhat.com> (raw)
In-Reply-To: <CAOakUfPchj=rAbtnh+ZUj0CERwgFLKKtzB5ozu4j-b0U6y9V=Q@mail.gmail.com>
On 04/07/2021 18.58, Richard Zak wrote:
>
> În dum., 4 iul. 2021 la 12:51, Thomas Huth <thuth@redhat.com
> <mailto:thuth@redhat.com>> a scris:
>
> On 04/07/2021 18.39, Richard Zak wrote:
> > Regarding upside down text, where did that occur? I certainly didn't
> do that
> > intentionally. Maybe an encoding error somewhere?
>
> That was meant as a humorous way to say that you should avoid top posting,
> but apparently it was just confusing instead. Sorry for that. Anyway, we
> use
> interleaved posting on qemu-devel. See e.g.:
>
> https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
> <https://en.wikipedia.org/wiki/Posting_style#Interleaved_style>
>
> Thomas
>
> Ahh got it. I hadn't done that since Gmail wants to hide the test I'm
> responding to. I'm assuming that revisions to a patch should still be a new
> post, not in a reply?
Right, different revisions should go into a new post, with a version
indication in the subject, e.g:
[PATCH v3] Fix for Haiku
Thomas
next prev parent reply other threads:[~2021-07-04 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 21:10 [PATCH 1/2] Fix for Haiku Richard Zak
2021-07-03 21:39 ` Peter Maydell
2021-07-03 22:06 ` Richard Zak
2021-07-04 9:03 ` Philippe Mathieu-Daudé
2021-07-04 9:27 ` Philippe Mathieu-Daudé
2021-07-04 9:30 ` Philippe Mathieu-Daudé
2021-07-04 14:20 ` Richard Zak
2021-07-04 16:16 ` Thomas Huth
2021-07-04 16:39 ` Richard Zak
2021-07-04 16:51 ` Thomas Huth
2021-07-04 16:58 ` Richard Zak
2021-07-04 18:34 ` Thomas Huth [this message]
2021-07-04 7:29 ` 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=020c0056-deb1-9f2b-29a4-a3c8a7ac266f@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.j.zak@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 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).