From: Mike Marshall <hubcap@omnibond.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Martin Brandenburg <martin@omnibond.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Mike Marshall <hubcap@omnibond.com>
Subject: Re: Orangefs, v4.5 and the merge window...
Date: Fri, 25 Mar 2016 21:07:08 -0400 [thread overview]
Message-ID: <CAOg9mSRi2RWALdW7X-FVvZ+qaxoaAOKPg9PrnNAA5rQAbHxW3w@mail.gmail.com> (raw)
In-Reply-To: <20160326010140.GN17997@ZenIV.linux.org.uk>
If Al's patches load on top of Martin's patches without conflict, I can probably
get it all merged and minimally tested before noon my time (eastern
US) tomorrow... that's probably late for where y'all are though...
-Mike
On Fri, Mar 25, 2016 at 9:01 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Fri, Mar 25, 2016 at 05:28:33PM -0700, Linus Torvalds wrote:
>> Gaah. I'm going to be traveling starting tomorrow night (red-eye) and I was
>> going to cut rc1 tomorrow and then really hope for a calm rc2 week.
>>
>> At the same time, is live to get this finally merged, about a year after I
>> originally thought were would. So I guess I'll take it, even if I hate the
>> timing.
>
> Umm... IIRC, there had been precedents when self-contained driver got merged
> later than -rc1. Might make more sense than rushing the merge in the last
> day of the window, especially since you are travelling...
>
>> There are zero changes outside orangefs itself, and obviously the
>> Makefile/KConfig file to get it all enabled?
>
> Yes.
next prev parent reply other threads:[~2016-03-26 1:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 20:18 Orangefs, v4.5 and the merge window Mike Marshall
2016-03-11 21:47 ` Al Viro
2016-03-11 22:35 ` Mike Marshall
2016-03-14 21:03 ` Mike Marshall
2016-03-26 0:21 ` Al Viro
2016-03-26 1:00 ` Mike Marshall
[not found] ` <CA+55aFzLC_pdj_ds82YYab5D7jpYMj26s0Frofxxhk=j7SqnjA@mail.gmail.com>
2016-03-26 1:01 ` Al Viro
2016-03-26 1:07 ` Mike Marshall [this message]
[not found] ` <CA+55aFysWS9mP+QgfAR6LZpEbkp61MUPQu0zDoq7cafmr3M8SA@mail.gmail.com>
2016-03-26 3:55 ` Mike Marshall
2016-03-26 4:30 ` Al Viro
2016-03-26 12:07 ` Mike Marshall
2016-03-26 14:47 ` Al Viro
2016-03-26 15:34 ` Mike Marshall
2016-03-26 15:50 ` Al Viro
2016-03-26 17:36 ` Mike Marshall
2016-03-26 18:28 ` Al Viro
2016-03-26 18:37 ` Al Viro
2016-03-26 19:00 ` Mike Marshall
2016-03-26 19:51 ` Linus Torvalds
2016-03-26 20:47 ` Mike Marshall
2016-03-26 21:00 ` Linus Torvalds
2016-03-26 1:02 ` Mike Marshall
2016-03-15 4:04 ` Martin Brandenburg
2016-03-15 16:45 ` Martin Brandenburg
2016-03-17 20:45 ` [PATCH] orangefs: getattr work (was: Re: Orangefs, v4.5 and the merge window...) Martin Brandenburg
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=CAOg9mSRi2RWALdW7X-FVvZ+qaxoaAOKPg9PrnNAA5rQAbHxW3w@mail.gmail.com \
--to=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.com \
--cc=torvalds@linux-foundation.org \
--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 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.