qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Move block format drivers to new directory 'bdrv'
Date: Mon, 27 Apr 2009 14:52:00 +0100	[thread overview]
Message-ID: <20090427135200.GA4885@shareable.org> (raw)
In-Reply-To: <49F5A1A9.2030704@redhat.com>

Kevin Wolf wrote:
> We should be careful not to put each file into its own directory. A 
> layout is good if it helps me to find the right file more quickly. If I 
> have the same problem finding the right directory (or just having to 
> change the working directory all the time) afterwards, I think it's not 
> worth the effort.

The way Linux dealt with this is long ago there were only a few
directories in drivers/ and a few top-level directories.  Block
devices went in drivers/block/, most other devices in drivers/char,
and there were only a few top-level directories.

That went on for many years.  Then as the number of drivers and kernel
subsystems grew too big, they added more and more specialised
directories.  Now we have a lot of directories under drivers/, and a
few more at the top level.

With GIT handling renames, adding more directories in future as needed
and moving things into them might be quite straightforward, I'm not
sure.

-- Jamie

  reply	other threads:[~2009-04-27 13:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 15:19 [Qemu-devel] [PATCH] Move block format drivers to new directory 'bdrv' Avi Kivity
2009-04-26 15:29 ` Christoph Hellwig
2009-04-26 15:55   ` Avi Kivity
2009-04-26 16:18     ` Blue Swirl
2009-04-26 16:20       ` Avi Kivity
2009-04-26 16:40         ` Blue Swirl
2009-04-26 17:04           ` Avi Kivity
2009-04-26 17:44           ` Anthony Liguori
2009-04-26 17:56             ` Christoph Hellwig
2009-04-26 18:06               ` Avi Kivity
2009-04-26 17:41         ` Anthony Liguori
2009-04-26 18:10           ` Blue Swirl
2009-04-26 21:26             ` Stefan Weil
2009-04-27 12:14             ` Kevin Wolf
2009-04-27 13:52               ` Jamie Lokier [this message]
2009-04-27 14:37                 ` M. Warner Losh
2009-04-27 12:08 ` Kevin Wolf
2009-04-27 12:10   ` Avi Kivity
2009-04-27 12:17     ` Kevin Wolf
2009-05-02 10:34   ` Stuart Brady

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=20090427135200.GA4885@shareable.org \
    --to=jamie@shareable.org \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=hch@lst.de \
    --cc=kwolf@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 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).