From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: yu.ning@linux.intel.com, pbonzini@redhat.com, eblake@redhat.com
Subject: [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post
Date: Wed, 29 Nov 2017 12:00:13 +0800 [thread overview]
Message-ID: <20171129040013.11804-1-famz@redhat.com> (raw)
Chances are qemu-devel@nongnu.org patches only adding new files can be
picked up by patchew and treated like a qemu.git patch. Patchew already
ignores [qemu-web] patches, so suggest it in this article as well. (Are
there better places to document this?)
Signed-off-by: Fam Zheng <famz@redhat.com>
---
_posts/2017-02-04-the-new-qemu-website-is-up.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/_posts/2017-02-04-the-new-qemu-website-is-up.md b/_posts/2017-02-04-the-new-qemu-website-is-up.md
index 66d3181..1758436 100644
--- a/_posts/2017-02-04-the-new-qemu-website-is-up.md
+++ b/_posts/2017-02-04-the-new-qemu-website-is-up.md
@@ -19,7 +19,9 @@ and the source code for the website can be cloned from the
repository. Just like for any other project hosted by QEMU, the best way
to propose or contribute a new change is by sending a patch through the
[qemu-devel@nongnu.org](https://lists.nongnu.org/mailman/listinfo/qemu-devel)
-mailing list.
+mailing list. (Add `[qemu-web PATCH]` to the subject so that CI will not be
+confused with qemu.git patches. You can run `git config format.subjectprefix
+'qemu-web PATCH'`, so that `git-send-email` command will do it for you.)
For example, if you would like to add a new screenshot to the homepage,
you can clone the `qemu-web.git` repository, add a PNG file to the
--
2.14.3
next reply other threads:[~2017-11-29 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 4:00 Fam Zheng [this message]
2017-11-29 9:16 ` [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post Paolo Bonzini
2017-11-29 15:18 ` Eric Blake
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=20171129040013.11804-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yu.ning@linux.intel.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).