[Qemu-devel] [PATCH qemu-web] Suggest qemu-web prefix in the introductory post

[Qemu-devel] [PATCH qemu-web] Suggest qemu-web prefix in the introductory post

[Fam Zheng]

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 | 3 ++-
 1 file changed, 2 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..c16053c 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,8 @@ 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.)
 
 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

Re: [Qemu-devel] [PATCH qemu-web] Suggest qemu-web prefix in the introductory post

[Eric Blake]

On 11/28/2017 07:58 PM, 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?)
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>   _posts/2017-02-04-the-new-qemu-website-is-up.md | 3 ++-
>   1 file changed, 2 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..c16053c 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,8 @@ 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.)
>   

I suggest mentioning that "git config format.subjectprefix 'qemu-web 
PATCH"' will automate that process, so you don't have to think about it 
when doing git send-email.

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

Re: [Qemu-devel] [PATCH qemu-web] Suggest qemu-web prefix in the introductory post

[Fam Zheng]

On Tue, 11/28 20:54, Eric Blake wrote:
> On 11/28/2017 07:58 PM, 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?)
> > 
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> >   _posts/2017-02-04-the-new-qemu-website-is-up.md | 3 ++-
> >   1 file changed, 2 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..c16053c 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,8 @@ 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.)
> 
> I suggest mentioning that "git config format.subjectprefix 'qemu-web PATCH"'
> will automate that process, so you don't have to think about it when doing
> git send-email.

Yes, I will send v2 and add that.

Fam