From: Fam Zheng <famz@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Announcement: Patchew server is online now
Date: Tue, 3 Mar 2015 15:05:24 +0800 [thread overview]
Message-ID: <20150303070524.GA15730@ad.nay.redhat.com> (raw)
In-Reply-To: <54F55155.80103@weilnetz.de>
On Tue, 03/03 07:14, Stefan Weil wrote:
> Am 28.02.2015 um 07:47 schrieb Fam Zheng:
> >Hello, everyone
> >
> >I'm glad to announce the fresh Patchew server deployment:
> >
> > http://qemu.patchew.org/
> >
> >The mission of this project is to help identify obvious defects (coding style,
> >compiling, etc.) of posted patches.
> >
> >Follow the green "passed" or red "failed" button in the page and you'll see the
> >testing log. You can also see which series have got reviews or comments.
> >
> >Q: How will this impact patch submission and merging process?
> >
> > Nothing is affected (at least for now), use this as an auxiliary.
> >
> >Q: What exactly are tested for each patch?
> >
> > * scripts/checkpatch.pl
> > * git am (on top of qemu.git)
>
> Obviously checkpatch.pl reports false positives because it tries to analyze
> quoted-printable UTF-8 e-mails. Here an example:
>
> http://qemu.patchew.org/testing/log/%3C1425214326-25326-1-git-send-email-sw@weilnetz.de%3E
Right.
The result was produced before I fixed the bug. I reran the test and now it's
passed.
Fam
next prev parent reply other threads:[~2015-03-03 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 6:47 [Qemu-devel] Announcement: Patchew server is online now Fam Zheng
2015-02-28 17:01 ` Stefan Weil
2015-03-02 9:03 ` Markus Armbruster
2015-03-02 9:12 ` Fam Zheng
2015-03-02 22:21 ` Stefan Hajnoczi
2015-03-03 6:14 ` Stefan Weil
2015-03-03 7:05 ` Fam Zheng [this message]
2015-03-03 7:20 ` Gerd Hoffmann
2015-03-03 7:36 ` Fam Zheng
2015-03-03 8:43 ` Gerd Hoffmann
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=20150303070524.GA15730@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).