linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] orangefs filesystem
Date: Sat, 8 Aug 2015 04:24:03 +0300	[thread overview]
Message-ID: <CA+55aFzVZ=nPKcdQge4xj1OHEuhpniYSu0GUE9FfxfeDcZdvcg@mail.gmail.com> (raw)
In-Reply-To: <CAOg9mSTUdX7AttveGdg952=LooqnPy_nXbdZLYvK2QyUexF+cg@mail.gmail.com>

On Sat, Aug 8, 2015 at 2:02 AM, Mike Marshall <hubcap@omnibond.com> wrote:
>> On Fri, Aug 7, 2015 at 4:44 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> The next step is to ask Stephen to add this to linux-next.
>
> Orangefs has been in linux-next for a couple of weeks and has
> had numerous improvements because of it...

Well, then the next step is:

 (a) explain to me why I should pull (which very much involves a
description of what orangefs is and who uses it)

     I use that for the merge message for the commit too, if/once I do
pull, so I want it for posterity as well, but most of all I want it
for actually knowing why, and not feeling like I have to go dig for
such core information.

 (b) doing the pull request during the merge window, because I'm
certainly not pulling a new filesystem into -rc6..

Ok?

                 Linus

  reply	other threads:[~2015-08-08  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 18:39 [GIT PULL] orangefs filesystem Mike Marshall
2015-08-07 20:44 ` Andrew Morton
2015-08-07 23:02   ` Mike Marshall
2015-08-08  1:24     ` Linus Torvalds [this message]
2015-08-08 15:26       ` Mike Marshall
2015-08-08 22:37         ` Jonathan Corbet

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='CA+55aFzVZ=nPKcdQge4xj1OHEuhpniYSu0GUE9FfxfeDcZdvcg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).