From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] CODING_STYLE amendments
Date: Thu, 26 Aug 2010 16:43:44 -0500 [thread overview]
Message-ID: <4C76E010.60505@codemonkey.ws> (raw)
In-Reply-To: <AANLkTinicqAyKATfWHMiibE5pc9wfrRF0L0GyrUpB9tp@mail.gmail.com>
On 08/26/2010 01:37 PM, Blue Swirl wrote:
> 1/5 and 2/5 updated according to review.
>
> I removed the contentious bool paragraph from 2/5, it can be added later.
>
> Blue Swirl (5):
> HACKING: add preprocessor rules
> HACKING: add C type rules
> HACKING: add memory management rules
> HACKING: add string management rules
> HACKING: add rules for printf-like functions
>
> CODING_STYLE | 3 -
> HACKING | 122 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 122 insertions(+), 3 deletions(-)
> create mode 100644 HACKING
>
Looks good!
Regards,
Anthony Liguori
prev parent reply other threads:[~2010-08-26 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 18:37 [Qemu-devel] [PATCH v3 0/5] CODING_STYLE amendments Blue Swirl
2010-08-26 21:43 ` 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=4C76E010.60505@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@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).