Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753898AbYJCRGb (ORCPT ); Fri, 3 Oct 2008 13:06:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752481AbYJCRGV (ORCPT ); Fri, 3 Oct 2008 13:06:21 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:53786 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752311AbYJCRGU (ORCPT ); Fri, 3 Oct 2008 13:06:20 -0400 Date: Fri, 3 Oct 2008 13:06:18 -0400 (EDT) From: Jan Engelhardt To: Chris Mason cc: linux-fsdevel , linux-kernel , Andrew Morton Subject: Re: [RFC] Btrfs mainline plans In-Reply-To: <1222717460.30627.56.camel@think.oraclecorp.com> Message-ID: References: <1222717460.30627.56.camel@think.oraclecorp.com> User-Agent: Alpine 1.10 (LNX 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 878 Lines: 21 On Monday 2008-09-29 15:44, Chris Mason wrote: >[...] >But, the code is very actively developed, and I believe the best way to >develop Btrfs from here is to get it into the mainline kernel (with a >large warning label about the disk format) and attract more extensive >review of both the disk format and underlying code. Definitely. While, due to the changing disk format, long-term storage is not really an option yet, the filesystem can be really useful in network-booted hybrid clients that have a local disk in an unionfs compound mount as a COW rw storage device (because RAM *is* limited after all). Keep up the work. Jan -- 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/