All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	John Snow <jsnow@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Patch checking bot
Date: Mon, 27 Oct 2014 19:25:10 +0100	[thread overview]
Message-ID: <544E8E06.6080804@suse.de> (raw)
In-Reply-To: <20141022100318.GC8798@stefanha-thinkpad.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

Hi,

Am 22.10.2014 um 12:03 schrieb Stefan Hajnoczi:
> On Mon, Oct 20, 2014 at 03:08:35PM +0100, Peter Maydell wrote:
>> On 20 October 2014 11:25, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>>> At KVM Forum 2014 we discussed a patch checking bot that automates patch
>>> format checking and smoke testing:
>>>
>>> 1. Did the patch submitter include Signed-off-by?
>>> 2. Does checkpatch.pl pass?
>>> 3. Does the patch apply to qemu.git/master?
>>> 4. Does each patch compile?
>>> 5. Does the series pass make check and qemu-iotests?
>>>
>>> Here are some thoughts on the patch checker:
>>>
>>> If a patch series passes successfully, no email is sent.  If a patch
>>> series fails, an email with the errors is sent as a reply to the patch
>>> series email thread.  The patch submitter can then respond in case there
>>> are false positive (e.g. from checkpatch.pl) - the bot doesn't care
>>> about replies but it tells the human reviewers and maintainers what the
>>> patch submitter intends to do.
>>
>> Probably also worth having a feature where the cover
>> letter or patch can have a "patchchecker: no" line in
>> it to tell the bot to ignore something, so people can
>> avoid it sending lots of mail for patch series they
>> know don't apply to mainline (eg ones which depend on
>> a previous series).
> 
> The bot would send 1 email reply with a report of all errors.  That
> doesn't seem too noisy.

Anthony had implemented that at some point and at times it spammed quite
a lot. No real objection, just reminding.

> That said, a header line to ignore the series is easy to implement so we
> might as well.

Anthony had simply detected [PATCH treename n/m] as not applying to
master iirc, which was also useful to human inbox readers.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-10-27 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 10:25 [Qemu-devel] Patch checking bot Stefan Hajnoczi
2014-10-20 14:08 ` Peter Maydell
2014-10-21 15:27   ` John Snow
2014-10-22 10:03   ` Stefan Hajnoczi
2014-10-27 18:25     ` Andreas Färber [this message]
2014-10-21  8:19 ` Fam Zheng
2014-10-22 10:08   ` Stefan Hajnoczi

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=544E8E06.6080804@suse.de \
    --to=afaerber@suse.de \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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.