Message ID | 6bbed95d83465dde644c6f66acc73e3cd94f123e.camel@hammerspace.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] Please pull NFS client changes for Linux 4.20. | expand |
On Fri, Oct 26, 2018 at 8:45 AM Trond Myklebust <trondmy@hammerspace.com> wrote: > > NFS client updates for Linux 4.20 Pulled. Btw, just out of curiosity - is there some pattern to when I get the pull requests from you vs Anna? Or is it just "whoever happens to have the baton"? Not that it matters, but I was wondering if there was some logic to it that I've missed.. Linus
On Fri, 2018-10-26 at 13:10 -0700, Linus Torvalds wrote: > On Fri, Oct 26, 2018 at 8:45 AM Trond Myklebust < > trondmy@hammerspace.com> wrote: > > > > NFS client updates for Linux 4.20 > > Pulled. Thank you! > Btw, just out of curiosity - is there some pattern to when I get the > pull requests from you vs Anna? Or is it just "whoever happens to > have > the baton"? Not that it matters, but I was wondering if there was > some > logic to it that I've missed.. We agreed about a year or so ago to take turns maintaining the linux- next branches. So in practice that means Anna has been sending you the pull requests for the odd kernel minor numbers, and I've been sending you the ones for the even numbers. We still share the burden of reviewing the code, though, so if something slips through the cracks, we get to share the blame... ☺ Cheers Trond
On Fri, Oct 26, 2018 at 1:21 PM Trond Myklebust <trondmy@hammerspace.com> wrote: > > We agreed about a year or so ago to take turns maintaining the linux- > next branches. Heh. That was a simpler pattern than I thought. It was just hidden by the fact that there are sometimes more than one pull request during the merge window, and then a variable number of "fixes" pull requests during the rc's.. But now that you mention it I can see that yeah, it just alternates by releases.. Linus