public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@zeniv•linux.org.uk>
Cc: Miklos Szeredi <miklos@szeredi•hu>,
	David Howells <dhowells@redhat•com>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Stefan Hajnoczi <stefanha@redhat•com>
Subject: Re: linux-next: manual merge of the vfs tree with the fuse tree
Date: Tue, 3 Sep 2019 09:23:17 +1000	[thread overview]
Message-ID: <20190903092317.3a3da7e1@canb.auug.org.au> (raw)
In-Reply-To: <20190902153004.GD1131@ZenIV.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

Hi Al,

On Mon, 2 Sep 2019 16:30:04 +0100 Al Viro <viro@zeniv•linux.org.uk> wrote:
>
> ... originals cheerfully dropped; will be gone in today's push to
> vfs.git#for-next.

Not pushed out yet?

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-09-02 23:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  3:01 linux-next: manual merge of the vfs tree with the fuse tree Stephen Rothwell
2019-09-02  9:00 ` Miklos Szeredi
2019-09-02 15:10   ` Miklos Szeredi
2019-09-02 15:30     ` Al Viro
2019-09-02 23:23       ` Stephen Rothwell [this message]
2019-09-02 23:29         ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2025-01-23 22:16 Stephen Rothwell
2020-02-06 22:14 Stephen Rothwell
2019-05-06 23:53 Stephen Rothwell
2019-05-08  1:01 ` 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=20190903092317.3a3da7e1@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dhowells@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=miklos@szeredi$(echo .)hu \
    --cc=stefanha@redhat$(echo .)com \
    --cc=viro@zeniv$(echo .)linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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