From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: manual merge of the vfs tree with the nfsd tree
Date: Mon, 8 Jul 2019 22:36:49 -0400 [thread overview]
Message-ID: <20190709023649.GC14439@fieldses.org> (raw)
In-Reply-To: <20190709001531.09b535d3@canb.auug.org.au>
On Tue, Jul 09, 2019 at 12:15:31AM +1000, Stephen Rothwell wrote:
> Hi,
>
> On Mon, 8 Jul 2019 08:45:10 -0400 "J. Bruce Fields" <bfields@fieldses.org> wrote:
> >
> > I did a fetch of
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> >
> > and looked at the "master" branch and couldn't find that vfs commit. Am
> > I looking in the wrong place?
>
> Maybe you were just a little early, I only finished linux-next today a
> few minutes before you sent this email.
Indeed, I see the merge now (ecd27e0ab735: Merge remote-tracking branch
'vfs/for-next'). Thanks!
--b.
>
> > (I'm sure your resolution is fine, I just thought to be careful it might
> > be nice to run some tests on the merge.)
>
> Thanks.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2019-07-09 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 1:06 linux-next: manual merge of the vfs tree with the nfsd tree Stephen Rothwell
2019-07-08 12:45 ` J. Bruce Fields
2019-07-08 14:15 ` Stephen Rothwell
2019-07-09 2:36 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-29 1:21 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=20190709023649.GC14439@fieldses.org \
--to=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox