From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, pbonzini@redhat.com, famz@redhat.com,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [qemu-web PATCH] Add a blog post about the release of version 2.10.0
Date: Fri, 1 Sep 2017 10:28:45 +0100 [thread overview]
Message-ID: <20170901092845.GF31680@redhat.com> (raw)
In-Reply-To: <150425055972.204.8095890686679875127@b5667b65043c>
On Fri, Sep 01, 2017 at 12:22:41AM -0700, no-reply@patchew.org wrote:
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Message-id: 1504250391-6353-1-git-send-email-thuth@redhat.com
> Subject: [Qemu-devel] [qemu-web PATCH] Add a blog post about the release of version 2.10.0
> Type: series
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
>
> BASE=base
> n=1
> total=$(git log --oneline $BASE.. | wc -l)
> failed=0
>
> git config --local diff.renamelimit 0
> git config --local diff.renames True
>
> commits="$(git log --format=%H --reverse $BASE..)"
> for c in $commits; do
> echo "Checking PATCH $n/$total: $(git log -n 1 --format=%s $c)..."
> if ! git show $c --format=email | ./scripts/checkpatch.pl --mailback -; then
> failed=1
> echo
> fi
> n=$((n+1))
> done
>
> exit $failed
> === TEST SCRIPT END ===
>
> Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
> From https://github.com/patchew-project/qemu
> * [new tag] patchew/1504250391-6353-1-git-send-email-thuth@redhat.com -> patchew/1504250391-6353-1-git-send-email-thuth@redhat.com
> Switched to a new branch 'test'
> b70b83ae5d Add a blog post about the release of version 2.10.0
>
> === OUTPUT BEGIN ===
> Checking PATCH 1/1: Add a blog post about the release of version 2.10.0...
> ERROR: trailing whitespace
> #60: FILE: _posts/2017-09-01-qemu-2-10-0.md:43:
> + * s390: support for z14 CPU models and netboot/TFTP via CCW BIOS, $
>
> total: 1 errors, 0 warnings, 56 lines checked
While it is nice that it identified the trailing whitespace in this
case, does it really make sense for the patchew to be running the
checkpatch.pl from qemu.git, against patches to qemu-web.git ?
Perhaps it should skip patches with 'web' or 'qemu-web' in the
[...] part of the subject ?
And/or have a dedicated patch checker for the web contnt that
ran appropriate tests ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-01 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 7:19 [Qemu-devel] [qemu-web PATCH] Add a blog post about the release of version 2.10.0 Thomas Huth
2017-09-01 7:22 ` no-reply
2017-09-01 9:28 ` Daniel P. Berrange [this message]
2017-09-01 10:41 ` Thomas Huth
2017-09-01 11:31 ` Fam Zheng
2017-09-02 13:43 ` Michael Roth
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=20170901092845.GF31680@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.