qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: qemu-devel@nongnu.org, bifferos <bifferos@yahoo.co.uk>
Subject: Re: [Qemu-devel] [PATCH] Add support for r6040 NIC
Date: Wed, 31 Aug 2011 14:23:09 -0500	[thread overview]
Message-ID: <4E5E8A1D.6020103@codemonkey.ws> (raw)
In-Reply-To: <20110831191206.GD17959@zapo>

On 08/31/2011 02:12 PM, Edgar E. Iglesias wrote:
> On Wed, Aug 31, 2011 at 01:48:34PM -0500, Anthony Liguori wrote:
>>> etc, etc. IMO, those bring codingstyle issues into the pretty much
>>> neglectable space.
>>
>> I don't think we lack contributors.  Documentation and tests are
>> really about discipline.  If we can't even be bothered to maintain
>> consistency in variable naming, do you really expected that we can
>> be disciplined in writing documentation and tests?
>
> Yes I do. It's not white and black, it's not about making the code
> completely inconsistent or 100 consistent. It's about find a level
> of consistency that is acceptable and doesn't cost too much to
> maintain.

I actually agree.  I don't like the idea of absolutely enforcing a 
coding style that demands no white space at the end of a line (if you 
can't see it, why in the world would you care?).

But coding style deviations that make the code look foreign, like using 
CamelCase for field names, seems important to me.

And I respect that other things seem important to other people (even 
invisible things like trailing white space).  So even though I wouldn't 
want to reject a patch because of coding style in some cases, I think 
it's important that we do our best to enforce it.

Regards,

Anthony Liguori

  parent reply	other threads:[~2011-08-31 19:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  1:05 [Qemu-devel] [PATCH] Add support for r6040 NIC bifferos
2011-08-31  1:17 ` Anthony Liguori
2011-08-31  1:30   ` malc
2011-08-31  1:59     ` Anthony Liguori
2011-08-31 13:17       ` malc
2011-08-31 13:30         ` Anthony Liguori
2011-08-31 13:39           ` malc
2011-08-31 13:40             ` Anthony Liguori
2011-08-31 13:51               ` malc
2011-08-31 14:29                 ` Anthony Liguori
2011-08-31 14:35                   ` malc
2011-08-31 16:06                     ` Anthony Liguori
2011-08-31 16:24                       ` malc
2011-08-31 18:35                         ` Blue Swirl
2011-08-31 18:37                           ` malc
2011-08-31 17:59                       ` Edgar E. Iglesias
2011-08-31 18:46                         ` Blue Swirl
2011-08-31 18:58                           ` Edgar E. Iglesias
2011-08-31 18:48                         ` Anthony Liguori
2011-08-31 19:12                           ` Edgar E. Iglesias
2011-08-31 19:18                             ` Edgar E. Iglesias
2011-08-31 19:23                             ` Anthony Liguori [this message]
2011-08-31 19:52                               ` Blue Swirl
2011-08-31 18:30                       ` Blue Swirl
2011-08-31 21:23                         ` bifferos
2011-09-01  7:39                         ` Markus Armbruster
2011-09-01 21:49                           ` Anthony Liguori
2011-09-03  9:44                             ` Blue Swirl
2011-09-01 10:42                       ` Gerd Hoffmann
2011-08-31 13:35         ` bifferos
2011-08-31 20:03     ` [Qemu-devel] [PATCH v2] " bifferos
2011-09-01  8:43 ` [Qemu-devel] [PATCH] " Avi Kivity
2011-09-01 20:02   ` bifferos

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=4E5E8A1D.6020103@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=bifferos@yahoo.co.uk \
    --cc=edgar.iglesias@gmail.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 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).