From: Kevin Wolf <kwolf@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Move block format drivers to new directory 'bdrv'
Date: Mon, 27 Apr 2009 14:14:33 +0200 [thread overview]
Message-ID: <49F5A1A9.2030704@redhat.com> (raw)
In-Reply-To: <f43fc5580904261110g741a4865ld6d36995514bd18c@mail.gmail.com>
Blue Swirl schrieb:
> hw could be arranged the same way, renamed to 'target':
>
> target
> |-- audio
> |-- block
> |-- bluetooth
> |-- boards
> | |-- alpha
> | |-- arm
> | |-- cris
> | |-- i386
> | |-- m68k
> | |-- mips
> | |-- ppc
> | |-- sh4
> | |-- sparc
> | |-- sparc64
> | `-- x86_64
> |-- input
> |-- irq
> |-- isa
> |-- mtd
> |-- net
> |-- pci
> |-- scsi
> |-- serial
> |-- timer
> |-- usb
> |-- video
> `-- xen
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.
Kevin
next prev parent reply other threads:[~2009-04-27 12:15 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 [this message]
2009-04-27 13:52 ` Jamie Lokier
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=49F5A1A9.2030704@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=hch@lst.de \
--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).