qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] Document QEMU coding style (v2)
Date: Sun, 05 Apr 2009 12:40:32 -0500	[thread overview]
Message-ID: <49D8ED10.6060600@us.ibm.com> (raw)
In-Reply-To: <1238520186-2636-1-git-send-email-avi@redhat.com>

Avi Kivity wrote:
> With the help of some Limoncino I noted several aspects of the QEMU coding
> style, particularly where it differs from the Linux coding style as many
> contributors work on both projects.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>

Applied.  Thanks.

Regards,

Anthony Liguori

      parent reply	other threads:[~2009-04-05 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 17:23 [Qemu-devel] [PATCH] Document QEMU coding style (v2) Avi Kivity
2009-04-01 13:38 ` Edgar E. Iglesias
2009-04-01 14:13   ` Laurent Vivier
2009-04-01 14:25     ` John Haxby
2009-04-01 15:47       ` Avi Kivity
2009-04-01 15:35   ` malc
2009-04-05 17:40 ` Anthony Liguori [this message]

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=49D8ED10.6060600@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@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 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).