Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760429AbYBRN3z (ORCPT ); Mon, 18 Feb 2008 08:29:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758321AbYBRN3f (ORCPT ); Mon, 18 Feb 2008 08:29:35 -0500 Received: from www.church-of-our-saviour.org ([69.25.196.31]:37048 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752488AbYBRN3d (ORCPT ); Mon, 18 Feb 2008 08:29:33 -0500 Date: Mon, 18 Feb 2008 08:28:58 -0500 From: Theodore Tso To: Adrian Bunk Cc: Ingo Molnar , Andreas Dilger , sct@redhat.com, akpm@linux-foundation.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [2.6 patch] fs/jbd/journal.c: cleanups Message-ID: <20080218132858.GA12568@mit.edu> Mail-Followup-To: Theodore Tso , Adrian Bunk , Ingo Molnar , Andreas Dilger , sct@redhat.com, akpm@linux-foundation.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org References: <20080217081935.GN3848@cs181133002.pp.htv.fi> <20080218070439.GG3029@webber.adilger.int> <20080218071229.GA1459@elte.hu> <20080218114936.GM8905@mit.edu> <20080218131209.GB21080@cs181133002.pp.htv.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080218131209.GB21080@cs181133002.pp.htv.fi> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@mit.edu X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1004 Lines: 22 On Mon, Feb 18, 2008 at 03:12:09PM +0200, Adrian Bunk wrote: > If me resending this old patch collides with something finally getting a > user this part of my patch shouldn't be applied now (but you might get > it again in 6 months if it's still unused...). > > But generally such conflicts would become visible if "known development > trees that are intended for mainline" were in -mm. It *has* been in -mm, except for periods when akpm has dropped it due to conflicts due to the "must have an in-tree user" doctrinaire attitude due to a conflict with the r/o bind patch. Did you actually try to do a compile test, or only made sure the patch would apply? The patch won't collide at application time, but it would when you compile it.... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/