From: Kevin Wolf <kwolf@redhat.com>
To: malc <av1474@comtv.ru>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Filip Navara <filip.navara@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix QCOW2 debugging code to compile again
Date: Wed, 24 Jun 2009 09:13:06 +0200 [thread overview]
Message-ID: <4A41D202.6070608@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906232138060.6501@linmac.oyster.ru>
malc schrieb:
> On Tue, 23 Jun 2009, Blue Swirl wrote:
>
>> On T, Filip Navara <filip.navara@gmail.com> wrote:
>>> Signed-off-by: Filip Navara <filip.navara@gmail.com>
>>> -//#define DEBUG_ALLOC
>>> -//#define DEBUG_ALLOC2
>>> -//#define DEBUG_EXT
>>> +/* #define DEBUG_ALLOC */
>>> +/* #define DEBUG_ALLOC2 */
>>> +/* #define DEBUG_EXT */
>> The C99 comment version is much more convenient than K&R comment
>> version in cases like this, where the intention is to be able to
>> enable the define quickly.
I agree.
> It's all the same for me: C-u A-;
You're not alone in the world.
Kevin
prev parent reply other threads:[~2009-06-24 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 15:25 [Qemu-devel] [PATCH] Fix QCOW2 debugging code to compile again Filip Navara
2009-06-23 16:29 ` Blue Swirl
2009-06-23 17:42 ` malc
2009-06-24 7:13 ` Kevin Wolf [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=4A41D202.6070608@redhat.com \
--to=kwolf@redhat.com \
--cc=av1474@comtv.ru \
--cc=blauwirbel@gmail.com \
--cc=filip.navara@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).