From: Stefan Hajnoczi <stefanha@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] checkpatch: warn about missing MAINTAINERS file changes
Date: Tue, 13 Mar 2018 10:37:36 +0000 [thread overview]
Message-ID: <20180313103736.GC16582@stefanha-x1.localdomain> (raw)
In-Reply-To: <43378184-a291-263f-b8b2-dedc455622e3@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2345 bytes --]
On Mon, Mar 12, 2018 at 02:46:20PM +0100, Thomas Huth wrote:
> On 12.03.2018 14:18, Stefan Hajnoczi wrote:
> > Warn if files are added/renamed/deleted without MAINTAINERS file
> > changes. This has helped me in Linux and we could benefit from this
> > check in QEMU.
> >
> > This patch is a manual cherry-pick of Linux commit
> > 13f1937ef33950b1112049972249e6191b82e6c9 ("checkpatch: emit a warning on
> > file add/move/delete") by Joe Perches <joe@perches.com>.
> >
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> > Note the 80-char lines are from upstream code. Keep them as-is.
> >
> > scripts/checkpatch.pl | 19 +++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> >
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index d1fe79bcc4..d0d8f63d48 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -1177,6 +1177,7 @@ sub process {
> > our $clean = 1;
> > my $signoff = 0;
> > my $is_patch = 0;
> > + my $reported_maintainer_file = 0;
> >
> > our @report = ();
> > our $cnt_lines = 0;
> > @@ -1379,6 +1380,24 @@ sub process {
> > }
> > }
> >
> > +# Check if MAINTAINERS is being updated. If so, there's probably no need to
> > +# emit the "does MAINTAINERS need updating?" message on file add/move/delete
> > + if ($line =~ /^\s*MAINTAINERS\s*\|/) {
> > + $reported_maintainer_file = 1;
> > + }
> > +
> > +# Check for added, moved or deleted files
> > + if (!$reported_maintainer_file &&
> > + ($line =~ /^(?:new|deleted) file mode\s*\d+\s*$/ ||
> > + $line =~ /^rename (?:from|to) [\w\/\.\-]+\s*$/ ||
> > + ($line =~ /\{\s*([\w\/\.\-]*)\s*\=\>\s*([\w\/\.\-]*)\s*\}/ &&
> > + (defined($1) || defined($2))))) {
> > + $is_patch = 1;
> > + $reported_maintainer_file = 1;
> > + WARN("added, moved or deleted file(s), does MAINTAINERS need updating?\n" .
> > + $herecurr);
>
> Could you please turn this into a notification instead of a warning? For
> rationale, please see the discussion of this patch last year:
>
> http://lists.gnu.org/archive/html/qemu-devel/2017-01/msg05753.html
It's a warning, not an error, so this already means "don't treat it as
fatal".
Why is a warning a bad user experience but a notification would be fine?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-03-13 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 13:18 [Qemu-devel] [PATCH] checkpatch: warn about missing MAINTAINERS file changes Stefan Hajnoczi
2018-03-12 13:33 ` Marc-André Lureau
2018-03-12 13:34 ` Peter Maydell
2018-04-16 14:11 ` Markus Armbruster
2018-04-16 14:28 ` Peter Maydell
2018-04-16 16:11 ` Markus Armbruster
2018-03-12 13:46 ` Thomas Huth
2018-03-13 10:37 ` Stefan Hajnoczi [this message]
2018-03-13 10:49 ` Thomas Huth
2018-03-15 11:50 ` Stefan Hajnoczi
2018-04-16 14:09 ` Markus Armbruster
2018-04-19 2:06 ` Fam Zheng
2018-04-19 5:08 ` Thomas Huth
2018-03-12 17:58 ` no-reply
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=20180313103736.GC16582@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).