All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] directory hierarchy
Date: Sun, 16 Sep 2012 09:40:40 -0500	[thread overview]
Message-ID: <87r4q2ni8n.fsf@codemonkey.ws> (raw)
In-Reply-To: <505336E0.6010509@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> writes:

> Il 14/09/2012 15:36, Peter Maydell ha scritto:
>> On 14 September 2012 14:17, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>> here is a proposal for moving around 150 C files currently in the
>>> toplevel directory to separate, well-delimited subdirectories.
>> 
>> No general objection (though some specific comments below). However
>> I think it would be helpful if you could provide some descriptions of
>> how your new subdirectories are defined. Otherwise the "well-delimited"
>> bit is largely in your head and future new files aren't likely to
>> respect it except by accident :-)
>
> Good question.  I just tried to use some taste, so well-delimited is a
> bit of a lie.  I mostly care that sysemu/, tools/, qga/ and user/ are
> well-delimited, i.e. executables do not have sources from other
> executables' directories, and similarly common/ is just for emulators.
>
>>> Header
>>> files would be moved for now in include/, preparing for subsequent
>>> reorganization of headers.
>> 
>> Just in include/, or in include/qemu/ ? (IIRC Anthony was hoping
>> to only move cleaned-up headers in there?)
>
> I dislike include/qemu, for the same reason I dislike qemu-*. :)

It's good to put includes in a single direction such that you can do
-Iinclude and then:

#include "qemu/foo.h"

Which is better than:

#include "foo.h"

Because the later can create confusion/conflict with system headers
whereas the former is (hopefully) completely unambiguous.

> Moving to include/ would be to clean up the top-level directory, withour
> touching the source code.  If something can be moved directly to one of
> the new source directories, that's also fine but I don't have high
> hopes.

I actually thinking moving to -Iinclude is a Good Thing for now because
it avoids touching a bunch of .c files.  In the longer term, we should
continue to clean up headers and move them into qemu/ though.

Regards,

Anthony Liguori

  reply	other threads:[~2012-09-16 14:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 13:17 [Qemu-devel] directory hierarchy Paolo Bonzini
2012-09-14 13:36 ` Peter Maydell
2012-09-14 13:53   ` Paolo Bonzini
2012-09-16 14:40     ` Anthony Liguori [this message]
2012-09-17  7:47       ` Paolo Bonzini
2012-09-14 13:44 ` Luiz Capitulino
2012-09-14 14:03   ` Paolo Bonzini
2012-09-14 13:47 ` Daniel P. Berrange
2012-09-14 13:57   ` Paolo Bonzini
2012-09-14 13:48 ` Peter Maydell
2012-09-14 13:55   ` Paolo Bonzini
2012-09-14 14:00     ` Peter Maydell
2012-09-14 14:37 ` Stefan Weil
2012-09-14 16:36   ` Paolo Bonzini
2012-09-14 16:09 ` Kevin Wolf
2012-09-14 16:45   ` Paolo Bonzini
2012-09-14 19:51 ` Blue Swirl
2012-09-14 21:28   ` Paolo Bonzini
2012-09-19 12:54   ` Avi Kivity
2012-09-19 19:57     ` Blue Swirl
2012-09-20 11:31       ` Avi Kivity
2012-09-22 13:15         ` Blue Swirl
2012-09-23  8:25           ` Avi Kivity
2012-09-23 16:07             ` Blue Swirl
2012-09-24  9:54               ` Avi Kivity
2012-09-16 14:44 ` Anthony Liguori
2012-09-17  7:52   ` Paolo Bonzini
2012-09-17 13:04     ` Anthony Liguori

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=87r4q2ni8n.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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.