From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 3/5] CODING_STYLE: add memory management rules
Date: Sun, 15 Aug 2010 10:07:26 -0400 [thread overview]
Message-ID: <4C67F49E.7080808@redhat.com> (raw)
In-Reply-To: <29F5076E-9189-4252-9808-A23CEB0A6969@web.de>
On 08/14/2010 10:52 AM, Andreas Färber wrote:
>>
>> Well, this is not coding style but architectural guide. We could
>> introduce a new document, rename CODING_STYLE or bury this to
>> qemu-tech.texi. But I still (optimistically) think that some kind of
>> READ_ME_BEFORE_CODING would help.
>
> I agree that we shouldn't overload CODING_STYLE.
>
> qemu-tech.texi historically was more a description of how QEMU works.
> Is there a reason not to simply put this FAQ/guide into the new Wiki?
> Otherwise we could stick with HACKING as file name.
If HACKING is chosen, it would anyway contain CODING_STYLE. I don't
have any preference as long as the content is kept in only one file.
Actually, I have a preference for CODING_STYLE since I see no reason to
rename a file (also considering git's rename tracking is not perfect).
Paolo
next prev parent reply other threads:[~2010-08-15 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 17:50 [Qemu-devel] [PATCH 3/5] CODING_STYLE: add memory management rules Blue Swirl
2010-08-13 19:24 ` [Qemu-devel] " Blue Swirl
2010-08-13 21:01 ` malc
2010-08-13 21:28 ` Blue Swirl
2010-08-13 21:56 ` malc
2010-08-14 10:02 ` Blue Swirl
2010-08-14 14:52 ` Andreas Färber
2010-08-15 14:07 ` Paolo Bonzini [this message]
2010-08-15 16:06 ` Avi Kivity
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=4C67F49E.7080808@redhat.com \
--to=pbonzini@redhat.com \
--cc=andreas.faerber@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.