qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kwolf@redhat.com, rene@exactcode.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] Multiboot support v2
Date: Thu, 18 Jun 2009 14:19:25 +0300	[thread overview]
Message-ID: <4A3A22BD.70201@redhat.com> (raw)
In-Reply-To: <662EA648-D416-4632-9095-DF622950E955@suse.de>

On 06/18/2009 01:22 PM, Alexander Graf wrote:
> Looking through pc.c I found for mostly without space, but if with 
> immediate space after it.
>

pc.c:

    [avi@cleopatra qemu-kvm (master)]$ grep -c -F 'if (' hw/pc.c
    99
    [avi@cleopatra qemu-kvm (master)]$ grep -c -F 'if(' hw/pc.c
    0
    [avi@cleopatra qemu-kvm (master)]$ grep -c -F 'for (' hw/pc.c
    13
    [avi@cleopatra qemu-kvm (master)]$ grep -c -F 'for(' hw/pc.c
    8


the entire tree:

    [avi@cleopatra qemu-kvm (1b443f4...)]$ git ls-files | xargs cat |
    grep -c -F 'if ('
    25831
    [avi@cleopatra qemu-kvm (1b443f4...)]$ git ls-files | xargs cat |
    grep -c -F 'if('
    711
    [avi@cleopatra qemu-kvm (1b443f4...)]$ git ls-files | xargs cat |
    grep -c -F 'for ('
    2085
    [avi@cleopatra qemu-kvm (1b443f4...)]$ git ls-files | xargs cat |
    grep -c -F 'for('
    906


The spaces win.

> Wouldn't it be more useful to write some automatic formatting script 
> git would run on patches that go in? Maybe people using tabs in the 
> wrong areas of the code would be able to submit patches by then too ;-).
>
> IMHO there is no real "qemu coding style" atm anyway - each maintainer 
> has his own and uses that for its subtree. It'd be a lot more helpful 
> to start addressing things at the root of the problems.
>

There's CODING_STYLE (which doesn't address this bit, but is a start).


-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-06-18 11:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 16:41 [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 1/4] Change bochs bios init order Alexander Graf
2009-06-17 16:41   ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg v2 Alexander Graf
2009-06-17 16:41     ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Alexander Graf
2009-06-17 16:41       ` [Qemu-devel] [PATCH 4/4] Multiboot build system Alexander Graf
2009-06-18  9:56       ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Avi Kivity
2009-06-18 10:22         ` Alexander Graf
2009-06-18 11:19           ` Avi Kivity [this message]
2009-06-17 17:10 ` [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 François Revol
2009-06-17 17:59   ` Anthony Liguori
2009-06-18  8:25     ` François Revol
2009-06-18  9:09       ` Kevin Wolf
2009-06-18 11:44         ` François Revol
2009-06-18 11:55           ` Alexander Graf
2009-06-18 12:13             ` François Revol
2009-06-18 12:01           ` Kevin Wolf
2009-06-18 12:17             ` François Revol
2009-06-18 12:23               ` Alexander Graf
2009-06-18 12:34                 ` François Revol
2009-06-18 12:29               ` Kevin Wolf
2009-06-18 12:35                 ` François Revol
2009-06-18 11:15 ` Gleb Natapov

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=4A3A22BD.70201@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rene@exactcode.de \
    /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).