From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sage Weil <sage@newdream.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: vfs tree build warning
Date: Mon, 18 Jan 2010 06:01:18 +0000 [thread overview]
Message-ID: <20100118060118.GT19799@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20100118164148.3452f553.sfr@canb.auug.org.au>
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@newdream.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.
next prev parent reply other threads:[~2010-01-18 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 2:11 linux-next: vfs tree build warning Stephen Rothwell
2010-01-18 4:34 ` Sage Weil
2010-01-18 5:41 ` Stephen Rothwell
2010-01-18 6:01 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 2:11 Stephen Rothwell
2010-01-18 14:34 ` Jörn Engel
2010-01-18 23:43 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100118060118.GT19799@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sage@newdream.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.