Yes, thanks, that clarifies some details for me. Paying attention to LWN is a good way to become aware of when the merge window opens, right? What has seemed counter-intuitive to me, as the maintainer of an out-of-tree filesystem, is that I should work to be ready for the merge window, but since that's when new features show up, that also might be when I'll find out about changes like dropping .read and .write from file_operations or changing readdir to iterate... I have posted orangefs as a patch to fs-devel several times, and I think the description that I send with the patch is what you need to see in my next pull request (during the merge window <g>)... Thanks again... -Mike On Fri, Aug 7, 2015 at 9:24 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Sat, Aug 8, 2015 at 2:02 AM, Mike Marshall <hubcap@xxxxxxxxxxxx> wrote: >>> On Fri, Aug 7, 2015 at 4:44 PM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
