All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post
@ 2017-11-29  4:00 Fam Zheng
  2017-11-29  9:16 ` Paolo Bonzini
  0 siblings, 1 reply; 3+ messages in thread
From: Fam Zheng @ 2017-11-29  4:00 UTC (permalink / raw)
  To: qemu-devel; +Cc: yu.ning, pbonzini, eblake

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

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post
  2017-11-29  4:00 [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post Fam Zheng
@ 2017-11-29  9:16 ` Paolo Bonzini
  2017-11-29 15:18   ` Eric Blake
  0 siblings, 1 reply; 3+ messages in thread
From: Paolo Bonzini @ 2017-11-29  9:16 UTC (permalink / raw)
  To: Fam Zheng, qemu-devel; +Cc: yu.ning, eblake

On 29/11/2017 05:00, Fam Zheng wrote:
> 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?)

Maybe the contribute page should have a link to the blog post?

Thanks,

Paolo

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post
  2017-11-29  9:16 ` Paolo Bonzini
@ 2017-11-29 15:18   ` Eric Blake
  0 siblings, 0 replies; 3+ messages in thread
From: Eric Blake @ 2017-11-29 15:18 UTC (permalink / raw)
  To: Paolo Bonzini, Fam Zheng, qemu-devel; +Cc: yu.ning

On 11/29/2017 03:16 AM, Paolo Bonzini wrote:
> On 29/11/2017 05:00, Fam Zheng wrote:
>> 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?)
> 
> Maybe the contribute page should have a link to the blog post?

Additionally, we should have a mention of qemu-web.git somewhere within 
qemu.git.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-11-29 15:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-29  4:00 [Qemu-devel] [PATCH qemu-web v2] Suggest qemu-web prefix in the introductory post Fam Zheng
2017-11-29  9:16 ` Paolo Bonzini
2017-11-29 15:18   ` Eric Blake

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.