Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Mar 2001 02:34:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Mar 2001 02:34:46 -0500 Received: from diamondhead.hesbynett.no ([212.33.144.138]:17669 "HELO diamondhead.hesbynett.no") by vger.kernel.org with SMTP id ; Thu, 8 Mar 2001 02:34:33 -0500 Message-ID: <61183.213.142.77.204.984044211.squirrel@diamond.no> Date: Thu, 8 Mar 2001 08:36:51 -0100 (GMT+1) Subject: 2.4.2-acX and reiserfs From: "zole@jblinux.net" To: linux-kernel@vger.kernel.org Reply-To: zole@jblinux.net X-Mailer: SquirrelMail (version 1.0.2) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I'm 99.9% certain that those patches referred to have been merged with the latest 2.4.2-acX, but just to make it 100% certain I'm asking this question. At www.namesys.com, the reiserfs website, I read: "Latest patch for linux-2.4.2 contains fixes for tail conversion bug, preallocated block leakage, object id sharing problem, dir fsync bug and other minor fixes/improvements." Have _all_ those fixes gone into the latest ac-patch? (I saw references to "tail conversion fixes" and "dir fsync bug" in Alan's Changelog, but I didn't find all of them so I'm not sure. :-) The reason of why I'm wondering is that I've been having serious trouble with reiserfs, and when I'm going for a new fresh installation I want to be 100% sure that all fixes have been merged. So I would really appreciate a confirmation that all fixes have been merged, so I won't have to worry. :-) Please reply to this email-address: zole@jblinux.net (as I'm not subscribed to the Linux kernel mailing-list as of now). Thanks a lot, Ole Andr? - 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/