From mboxrd@z Thu Jan  1 00:00:00 1970
From: Badari Pulavarty <pbadari@gmail.com>
Subject: Re: [ANNOUNCE] new new aops patchset
Date: Wed, 04 Apr 2007 16:02:27 -0700
Message-ID: <1175727747.5019.10.camel@dyn9047017100.beaverton.ibm.com>
References: <20070402120934.GA19626@wotan.suse.de>
	 <20070404221034.GF21982@ca-server1.us.oracle.com>
	 <1175726389.5019.4.camel@dyn9047017100.beaverton.ibm.com>
	 <20070404225123.GH21982@ca-server1.us.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Filesystems <linux-fsdevel@vger.kernel.org>,
	Steven Whitehouse <swhiteho@redhat.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from e32.co.us.ibm.com ([32.97.110.150]:41747 "EHLO
	e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752599AbXDDXCY (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 4 Apr 2007 19:02:24 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106])
	by e32.co.us.ibm.com (8.12.11.20060308/8.13.8) with ESMTP id l34N0AiZ018442
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Apr 2007 19:00:10 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l34N2Nhn191786
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Apr 2007 17:02:23 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l34N2Mvr030029
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Apr 2007 17:02:23 -0600
In-Reply-To: <20070404225123.GH21982@ca-server1.us.oracle.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Wed, 2007-04-04 at 15:51 -0700, Mark Fasheh wrote:
> On Wed, Apr 04, 2007 at 03:39:48PM -0700, Badari Pulavarty wrote:
> > Could you elaborate on issues ext3 caused ? Its pretty stable for
> > me (after bunch of simple fixes, I posted earlier). Anything I need
> > to be aware ?
> 
> Oh, I meant merge issues - that's all. And that's just because I was trying
> to be "fancy" by merging the stuff on top of a git branch I'm working on ;)
> 	--Mark

Okay, Thanks.