From: Oliver Neukum <oliver@neukum.name>
To: Shawn <core@enodev.com>
Cc: Shawn <core@enodev.com>, Christoph Hellwig <hch@infradead.org>,
Michael Clark <michael@metaparadigm.com>,
Mark Peloquin <markpeloquin@hotmail.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: Linux v2.5.42
Date: Tue, 15 Oct 2002 01:04:13 +0200 [thread overview]
Message-ID: <200210150104.13593.oliver@neukum.name> (raw)
In-Reply-To: <20021014175304.A28906@q.mn.rr.com>
> As I said before, edicts help no one. I appreciate your sentiment, and
> to some degree share it, but you have to take a non-cheerleader look at
> things like this.
I'd be happy if there were no such problem.
> > Besides people who compile their own kernels are not that unimportant.
>
> No one is saying that. No one is even saying that mainline inclusion
> isn't extremely beneficial to EVMS or DM. The question isn't whether DM
> or EVMS would be impacted more positively if it were included. The
> question is whether mainline would be better off including them, and not
> the other way around.
>
> Also, let me define the phrase "better off" to mean "better off W.R.T.
> design, architecture, overall code quality, abstractions in the right
> place, etc etc", and not to mean politically, as in, more users.
While these are important choices, Linux is an OS for practical use
and needs to meet some minimum of necessary features.
> Honestly though, if you aren't able to do the work it takes to be a 3rd
> party patch tester, it's less likely you can properly test or submit
> proper bug reports in the first place.
That's not the problem. There'd be bug reports from half a dozen vendor
kernels, one incorporating lvm2, the other evms and probably several
versions of them plus their own kernel patches.
A gigantic mess.
Regards
Oliver
next prev parent reply other threads:[~2002-10-14 22:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 17:14 Mark Peloquin
2002-10-12 19:34 ` Alan Cox
2002-10-12 19:37 ` jbradford
2002-10-13 23:55 ` Rob Landley
2002-10-13 12:41 ` [Evms-devel] " Michael Clark
2002-10-13 13:49 ` Christoph Hellwig
2002-10-13 15:16 ` Michael Clark
2002-10-13 15:35 ` Christoph Hellwig
2002-10-13 16:11 ` Brian Jackson
2002-10-13 16:26 ` Arjan van de Ven
2002-10-13 17:06 ` Brian Jackson
2002-10-13 19:58 ` Mark Hahn
2002-10-13 19:57 ` Rik van Riel
2002-10-13 20:26 ` Sean Neakums
2002-10-24 11:45 ` Alexander Kellett
2002-10-13 19:59 ` Andrew Morton
2002-10-13 20:24 ` Bernd Eckenfels
2002-10-14 15:11 ` Christoph Hellwig
2002-10-14 22:27 ` Bernd Eckenfels
2002-10-14 4:55 ` [Evms-devel] " Andreas Dilger
2002-10-13 17:46 ` Robert Love
2002-10-13 18:34 ` Brian Jackson
2002-10-14 4:23 ` [Evms-devel] " Andreas Dilger
2002-10-14 16:08 ` Christoph Hellwig
2002-10-14 14:45 ` Christoph Hellwig
2002-10-13 16:18 ` [Evms-devel] " Michael Clark
2002-10-13 17:10 ` Alexander Viro
2002-10-13 17:41 ` Michael Clark
2002-10-14 4:43 ` Andreas Dilger
2002-10-14 16:16 ` Christoph Hellwig
2002-10-14 15:21 ` Christoph Hellwig
2002-10-14 14:42 ` Shawn
2002-10-14 15:15 ` Christoph Hellwig
2002-10-14 14:20 ` Shawn
2002-10-14 16:15 ` Rik van Riel
2002-10-14 21:34 ` Shawn
2002-10-14 16:21 ` Christoph Hellwig
2002-10-14 16:38 ` Jeff Garzik
2002-10-14 21:47 ` Shawn
2002-10-15 7:42 ` Heinz J . Mauelshagen
2002-10-14 21:48 ` Oliver Neukum
2002-10-14 21:55 ` Shawn
2002-10-14 22:35 ` Oliver Neukum
2002-10-14 22:53 ` Shawn
2002-10-14 23:04 ` Oliver Neukum [this message]
2002-10-14 23:16 ` Alexander Viro
2002-10-14 23:30 ` Oliver Neukum
2002-10-15 0:10 ` Andrew Clausen
2002-10-14 22:57 ` Alexander Viro
2002-10-13 13:41 ` Christoph Hellwig
2002-10-14 23:57 [Evms-devel] " Mark Peloquin
2002-10-15 14:51 Steve Pratt
2002-10-15 21:18 ` Andrew Clausen
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=200210150104.13593.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=core@enodev.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markpeloquin@hotmail.com \
--cc=michael@metaparadigm.com \
--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
all inboxes | Powered by JetHome®