[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100118060118.GT19799@ZenIV.linux.org.uk>
Date: Mon, 18 Jan 2010 06:01:18 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Sage Weil <sage@...dream.net>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: linux-next: vfs tree build warning
On Mon, Jan 18, 2010 at 04:41:48PM +1100, Stephen Rothwell wrote:
> Hi Sage,
>
> On Sun, 17 Jan 2010 20:34:29 -0800 (PST) Sage Weil <sage@...dream.net> wrote:
> >
> > I can put this in the for-next branch of the ceph tree.
>
> Not unless you first merge the vfs tree into the ceph tree ...
Grr... How about putting these two commits on a separate (and absolutely
unchanging) branch? I'd rather live without being unable to rediff
for-next if needed and that way nfs, ceph, etc. could pull _that_ instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists