From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id mAQ3RBmb002345 for ; Tue, 25 Nov 2008 21:27:11 -0600 Date: Tue, 25 Nov 2008 22:27:10 -0500 From: Christoph Hellwig Subject: Re: New XFS git tree on oss.sgi.com Message-ID: <20081126032710.GA19523@infradead.org> References: <492BA7AD.5080007@sgi.com> <20081125140553.GA16553@infradead.org> <492CA245.3000709@sgi.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <492CA245.3000709@sgi.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Lachlan McIlroy Cc: Christoph Hellwig , xfs@oss.sgi.com On Wed, Nov 26, 2008 at 12:11:33PM +1100, Lachlan McIlroy wrote: > Christoph Hellwig wrote: > > Looking over the -dev tree, can you please revert > > > > http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=commitdiff;h=c79ae33eebac1c15aa435fb77362fdc5eff2be4d > > > > All this wasn't needed in the old ptrace tree either, no need to carry it forward. > > Is this code needed for the BSD port? According to Russell it may be need, but he'll probably need a newer version than the one check-ed in once he resyncs. And he'll have his own support dir with the rest of the BSD code. > There may be other code that can be removed too. We moved a lot of the code > that existed only in ptools into the xfs-dev branch so that branch and ptools > are in sync. This allows us to automatically merge changes back to the old > ptools tree (yes it still lives). Any merge failures will now be handled > between git branches and not between different scms. The xfs-dev also fortunately doesn't have the modular quota code. So for both these I'd suggest removing them from the ptools tree, too. Also http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=commitdiff;h=ca830fdf6231d0683f4ea4e9223e234c3a509063 doesn't seem to be needed. None of those symbols seems to be used by either dmapi or xfsidbg, the only two modules using xfs symbols in the tree. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs