From: "Steve Pratt" <slpratt@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Kevin M Corry" <corryk@us.ibm.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: EVMS Submission for 2.5
Date: Thu, 3 Oct 2002 11:09:37 -0500 [thread overview]
Message-ID: <OF479E53F5.0433681B-ON85256C47.0057D3AF@pok.ibm.com> (raw)
Christoph Hellwig wrote:
>> subdirectories were created: drivers/evms/ for the main source code,
>> and include/linux/evms/ for the header files.
>What's the reason to not have the headers under drivers/evms.
None, really. Why does md put it's headers in include/linux/raid ???
We can put them wherever.
> And why don'T you just use drivers-md like all other volume management
drivers?
Because it is getting crowded. Why does every filesystem create it's own
directory in fs? Maybe drivers/vm/md drivers/vm/dm drivers/vm/evms would
be better. Again, we can put it wherever, this just seems like a logical
place.
Steve
next reply other threads:[~2002-10-03 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 16:09 Steve Pratt [this message]
2002-10-04 14:20 ` [Evms-devel] Re: EVMS Submission for 2.5 Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 16:13 Greg KH
2002-10-03 16:21 ` Alexander Viro
2002-10-03 16:30 ` Greg KH
2002-10-03 19:52 ` [Evms-devel] " Oliver Neukum
2002-10-03 21:37 ` Greg KH
2002-10-03 21:02 ` Oliver Neukum
2002-10-03 22:56 ` Greg KH
2002-10-03 23:03 ` Alexander Viro
2002-10-04 8:07 ` Oliver Neukum
2002-10-05 0:06 ` Greg KH
2002-10-02 21:33 Kevin Corry
2002-10-03 14:32 ` Christoph Hellwig
2002-10-03 14:59 ` [Evms-devel] " Michael Clark
2002-10-03 15:08 ` Christoph Hellwig
2002-10-03 15:03 ` Shawn
2002-10-03 15:31 ` Christoph Hellwig
2002-10-03 15:41 ` [Evms-devel] " Mike Tran
2002-10-04 0:39 ` Kevin Corry
2002-10-04 13:06 ` Alan Cox
2002-10-04 13:07 ` [Evms-devel] " Kevin Corry
2002-10-04 17:29 ` Kai Henningsen
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=OF479E53F5.0433681B-ON85256C47.0057D3AF@pok.ibm.com \
--to=slpratt@us.ibm.com \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).