From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 20 Apr 2001 11:34:19 +0100 From: Patrick Caulfield Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list Message-ID: <20010420113419.B569@tykepenguin.com> References: <20010419142400.E10345@sistina.com> <200104191945.f3JJjKRn015661@webber.adilger.int> <20010419145337.K10345@sistina.com> <3ADF45FC.EE7B2003@mandrakesoft.com> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <3ADF45FC.EE7B2003@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Apr 19, 2001 at 04:09:32PM -0400 Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com Cc: AJ Lewis , linux-kernel@vger.kernel.org, linux-openlvm@nl.linux.org On Thu, Apr 19, 2001 at 04:09:32PM -0400, Jeff Garzik wrote: > 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. OK, we're in the process of splitting the big patch up into nice clean small patches to go to Linus. Hopefully this should be done today, or very shortly at least. patrick