From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <xfs-bounce@oss.sgi.com>
Received: with ECARTIS (v1.0.0; list xfs); Mon, 19 May 2008 18:47:44 -0700 (PDT)
Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130])
	by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with SMTP id m4K1leEI002028
	for <xfs@oss.sgi.com>; Mon, 19 May 2008 18:47:41 -0700
Message-ID: <48322E58.8060009@sgi.com>
Date: Tue, 20 May 2008 11:50:16 +1000
From: Lachlan McIlroy <lachlan@sgi.com>
Reply-To: lachlan@sgi.com
MIME-Version: 1.0
Subject: Re: take messages
References: <20080518102710.GA17618@lst.de> <4830CA28.9060805@sgi.com> <20080519060022.GA15529@lst.de>
In-Reply-To: <20080519060022.GA15529@lst.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: xfs-bounce@oss.sgi.com
Errors-to: xfs-bounce@oss.sgi.com
List-Id: xfs
To: Christoph Hellwig <hch@lst.de>
Cc: Mark Goodwin <markgw@sgi.com>, xfs@oss.sgi.com

Christoph Hellwig wrote:
> On Mon, May 19, 2008 at 10:30:32AM +1000, Mark Goodwin wrote:
>> Christoph Hellwig wrote:
>>> folks, any chance to get take messages sent to the list, please? 
>> do you mean for any checkin, or just oss pushes?
> 
> Well, the oss pushes are automatic, so it should be sent with the
> actual commit.  Even better would be migrating XFS to a proper git
> tree with a commit trigger so that people can't accidentally forget it..

oss pushes automatic?  They could be but aren't.  Yes, migrating XFS
to a git tree is a great idea - one we have been talking about for
far too long...