From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, thuth@redhat.com, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] checkpatch: bump most warnings to errors
Date: Wed, 10 Aug 2016 03:08:33 -0400 (EDT) [thread overview]
Message-ID: <1550519450.770774.1470812913274.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <874m6t5d39.fsf@dusky.pond.sub.org>
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > This only leaves a warning-level message for extra-long lines, which
> > are relatively common and cause patchew to send email that will likely
> > be ignored.
> >
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Are we ready to give up on illegibly long lines?
We have other levels of code review than checkpatch. 80 chars can be
illegibly short in some circumstances where 83 or 84 are enough.
Paolo
> What happened to "[PATCH 2/4] CODING_STYLE, checkpatch: update line
> length rules"?
next prev parent reply other threads:[~2016-08-10 7:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 15:47 [Qemu-devel] [PATCH 0/3] checkpatch tweaks Paolo Bonzini
2016-08-09 15:47 ` [Qemu-devel] [PATCH 1/3] checkpatch: tweak the files in which TABs are checked Paolo Bonzini
2016-08-10 2:06 ` Fam Zheng
2016-08-10 6:46 ` Markus Armbruster
2016-08-10 7:32 ` Cornelia Huck
2016-08-09 15:47 ` [Qemu-devel] [PATCH 2/3] checkpatch: bump most warnings to errors Paolo Bonzini
2016-08-10 6:53 ` Markus Armbruster
2016-08-10 7:08 ` Paolo Bonzini [this message]
2016-08-10 7:48 ` Markus Armbruster
2016-08-10 7:58 ` Paolo Bonzini
2016-08-10 7:48 ` Cornelia Huck
2016-08-10 7:46 ` Cornelia Huck
2016-08-10 7:58 ` Paolo Bonzini
2016-08-09 15:47 ` [Qemu-devel] [PATCH 3/3] checkpatch: default to success if only warnings Paolo Bonzini
2016-08-10 2:10 ` [Qemu-devel] [PATCH 0/3] checkpatch tweaks Fam Zheng
2016-08-10 7:15 ` Christian Borntraeger
2016-08-10 7:52 ` Cornelia Huck
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=1550519450.770774.1470812913274.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@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 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).