All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] directory hierarchy
Date: Fri, 14 Sep 2012 15:57:58 +0200	[thread overview]
Message-ID: <505337E6.80801@redhat.com> (raw)
In-Reply-To: <20120914134724.GA6819@redhat.com>

Il 14/09/2012 15:47, Daniel P. Berrange ha scritto:
> On Fri, Sep 14, 2012 at 03:17:52PM +0200, Paolo Bonzini wrote:
>> Hi all,
>>
>> here is a proposal for moving around 150 C files currently in the
>> toplevel directory to separate, well-delimited subdirectories.  Header
>> files would be moved for now in include/, preparing for subsequent
>> reorganization of headers.
> 
> I tend to view usage of a separate 'include/' subdirectory as a
> location for public facing header files. For internal header
> files, IMHO, its nicer to just have them alongside the .c file
> which has the corresponding implementation.

Yes, me too, but unfortunately almost nothing follows this scheme in
QEMU.  Probably the hw/ files do, but I'm not touching those with a pole.

>> Usually the files would keep their names, but I loathe names starting
>> with qemu-* so I took the occasion to rename those.
> 
> Heh, I would have suggested the opposite - use a 'qemu-' prefix on
> every single file, mostly so that you avoid the confusion where a
> source-local header file happens to have same name as a public
> header file in /usr/include.

Note the above quote is about C files, not headers.

For headers, I would solve the confusion by moving them all in
subdirectories of include/, but not yet.  I want to keep source files
100% unchanged for now.

> I appauld your amibition to modularize the source tree layout
> more. Even if you disagree with my POV on the issues above, it
> would be an improvement.

Oh, on a fresh project I'd agree a lot.  Just trying to do things piecewise.

Paolo

  reply	other threads:[~2012-09-14 13:58 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
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 [this message]
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=505337E6.80801@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@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 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.