All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: update line length and mixed declaration rules
Date: Fri, 19 Jun 2015 10:38:21 +0200	[thread overview]
Message-ID: <5583D4FD.1000300@redhat.com> (raw)
In-Reply-To: <5583CE51.3020206@suse.de>



On 19/06/2015 10:09, Andreas Färber wrote:
>> > -Lines are 80 characters; not longer.
>> > +Lines should be 80 characters; try not to make them longer.
>> > +
>> > +Sometimes it is hard to do, especially when dealing with QEMU subsystems
>> > +that use long function or symbol names.  Even in that case, do not make
>> > +lines _much_ longer than 80 characters.
> Anthony had always allowed sensible exceptions to that rule, so +1 for
> reformulating it here.
> 
> However, I would suggest that in that case we should lower the
> recommendation/warning to 78 chars, with the rationale of not only the
> actual code but also two-way diffs (79 chars plus ±/space) and
> three-way diffs (78 chars plus 2x ±/space) fitting into standard 80x24
> windows.

Good idea.

> Either way, can you please decouple the two changes?

Sure, didn't want to spam people with a series on what is mostly an RFC.

Paolo

  reply	other threads:[~2015-06-19  8:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  7:29 [Qemu-devel] [PATCH] CODING_STYLE: update line length and mixed declaration rules Paolo Bonzini
2015-06-19  7:53 ` Thomas Huth
2015-06-19  7:55   ` Paolo Bonzini
2015-06-19  8:09 ` Andreas Färber
2015-06-19  8:38   ` Paolo Bonzini [this message]
2015-08-25 18:20     ` Markus Armbruster
2015-08-25 19:22       ` John Snow
2015-08-26  8:27         ` Markus Armbruster

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=5583D4FD.1000300@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.