public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: AJ Lewis <lewis@sistina.com>
Cc: linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
	linux-openlvm@nl.linux.org
Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Thu, 19 Apr 2001 16:09:32 -0400	[thread overview]
Message-ID: <3ADF45FC.EE7B2003@mandrakesoft.com> (raw)
In-Reply-To: <20010419142400.E10345@sistina.com> <200104191945.f3JJjKRn015661@webber.adilger.int> <20010419145337.K10345@sistina.com>

AJ Lewis wrote:
> Ok, the issue here is that we're trying to get a release out and so anything
> that majorly changes the code is getting shunted aside for the moment.  It
> would be stupid to just add everything that comes in on the ML without
> review.  Linus does the exact same thing.  I've said this before to you
> Andreas, but apparently you feel that you should have final say on whether
> your patches go in or not.

> As far as getting patches into the stock kernel, we've been sending patches
> to Linus for over a month now, and none of them have made it in.  Maybe
> someone has some pointers on how we get our code past his filters.

Read Documentation/SubmittingPatches, and also listen to kernel hackers
who know the block layer and want to fix lvm.

And I wonder, if kernel hackers are saying lvm is broken... why do you
want to freeze it and ship it in that state?

-- 
Jeff Garzik       | "The universe is like a safe to which there is a
Building 1024     |  combination -- but the combination is locked up
MandrakeSoft      |  in the safe."    -- Peter DeVries

  parent reply	other threads:[~2001-04-19 20:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 17:51 [repost] Announce: Linux-OpenLVM mailing list Jes Sorensen
2001-04-19 18:29 ` AJ Lewis
2001-04-19 18:34   ` Jeff Garzik
2001-04-19 18:35   ` Rik van Riel
2001-04-24 14:58     ` Heinz J. Mauelshagen
2001-04-19 18:48   ` Jens Axboe
2001-04-24 14:54     ` Heinz J. Mauelshagen
2001-04-19 19:02   ` Alan Cox
2001-04-19 19:24     ` AJ Lewis
2001-04-19 19:33       ` Jens Axboe
2001-04-19 19:46         ` Martin K. Petersen
2001-04-24 15:00           ` Heinz J. Mauelshagen
2001-04-19 19:35       ` Jes Sorensen
2001-04-19 19:44         ` AJ Lewis
2001-04-19 19:45       ` [linux-lvm] " Andreas Dilger
2001-04-19 19:51         ` Alan Cox
2001-04-19 19:53         ` Rik van Riel
2001-04-19 19:53         ` AJ Lewis
2001-04-19 19:56           ` Jens Axboe
2001-04-19 20:03           ` Alan Cox
2001-04-19 21:52             ` Miles Lane
2001-04-19 20:09           ` Jeff Garzik [this message]
2001-04-19 20:16             ` AJ Lewis
2001-04-20 10:34             ` Patrick Caulfield
2001-04-20  0:41           ` Andreas Dilger
2001-04-19 19:55         ` Christoph Hellwig
2001-04-20  1:29         ` Paul Jakma
2001-04-19 20:33       ` Miles Lane
2001-04-20 12:36         ` Doug McNaught
2001-04-20 22:55           ` Matti Aarnio
2001-04-21 20:45             ` Rik van Riel
2001-04-19 19:17   ` Jes Sorensen
2001-04-19 19:26     ` AJ Lewis
2001-04-19 19:40       ` Jes Sorensen
2001-04-19 19:19   ` Martin K. Petersen
2001-04-19 19:40   ` [linux-lvm] " AJ Lewis
2001-04-19 19:49     ` Alan Cox
2001-04-19 21:25     ` Kurt Garloff
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20  7:37 Luca Berra
2001-04-20  7:59 ` Jeff Garzik
     [not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` Heinz J. Mauelshagen
2001-04-20 17:39   ` [linux-lvm] " Wichert Akkerman

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=3ADF45FC.EE7B2003@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=lewis@sistina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=linux-openlvm@nl.linux.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