From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [GIT PULL] Btrfs for linux-next Date: Tue, 2 Oct 2012 08:26:53 -0400 Message-ID: <20121002122653.GB1140@shiny> References: <20120930115258.GA13506@shiny> <20121001181549.817cc2d7d0d660eb593922fd@canb.auug.org.au> <20121002013618.GA1140@shiny> <20121002125436.a39101ab6f87d4e8596c1031@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from mx1.fusionio.com ([66.114.96.30]:37670 "EHLO mx1.fusionio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752342Ab2JBM04 (ORCPT ); Tue, 2 Oct 2012 08:26:56 -0400 Content-Disposition: inline In-Reply-To: <20121002125436.a39101ab6f87d4e8596c1031@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Chris Mason , "linux-next@vger.kernel.org" On Mon, Oct 01, 2012 at 08:54:36PM -0600, Stephen Rothwell wrote: > Hi Chris, > > On Mon, 1 Oct 2012 21:36:18 -0400 Chris Mason wrote: > > > > Sorry for the hassle, we've updated that patch and rebased the tree: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next > > Looks good today. > > I am not sure if you are aware of exactly how linux-next works: I will > fetch that branch of your tree every morning, so any changes will be > automatically incorporated into linux-next. Thanks! I knew you'd pull again but wanted to send an explicit ack that we had fixed up the first pull. -chris