From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Shirley Ma <shirley.ma@oracle.com>
Cc: Anna Schumaker <Anna.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [GIT PULL] Please pull NFS client RDMA changes for 3.16
Date: Tue, 3 Jun 2014 19:07:59 -0400 [thread overview]
Message-ID: <CAHQdGtQdBjXCgQe62AV_Vm2uct9OtZw4t5AA3NKikA8_0rQ81A@mail.gmail.com> (raw)
In-Reply-To: <538E12B9.8030007@oracle.com>
On Tue, Jun 3, 2014 at 2:23 PM, Shirley Ma <shirley.ma@oracle.com> wrote:
>
>
> On 06/03/2014 10:53 AM, Trond Myklebust wrote:
>> On Tue, Jun 3, 2014 at 1:04 PM, Anna Schumaker
>> <Anna.Schumaker@netapp.com> wrote:
>>> I pulled from Chuck's branch earlier today before sending this. He has all the date stamps set as June 2.
>>>
>>
>> OK, this is broken and I'm not pulling. The point of asking you to
>> maintain the tree was to ensure that the patches get reviewed by you,
>> and that I have signed-off-bys etc showing that is the case.
>
> Thanks Trond for checking. Where was broken? What we can help here?
Hi Shirley,
I meant that the process was broken, since I was losing the
information about what Anna had reviewed and so the issue was how to
fix that. I've now talked to Chuck and Anna and we've set up a model
for how to work together in the future: the model I'd like to see is
for Anna to publish a branch of patches that she has reviewed, with
the signed-off-by line. That way I know that the contents are the
exact same patches that were approved on the mailing lists.
Cheers
Trond
>>> On 06/03/2014 12:44 PM, Trond Myklebust wrote:
>>>> On Tue, Jun 3, 2014 at 11:59 AM, Anna Schumaker
>>>> <Anna.Schumaker@netapp.com> wrote:
>>>>> Hey Trond,
>>>>>
>>>>> The following changes since commit fad01e866afdbe01a1f3ec06a39c3a8b9e197014:
>>>>>
>>>>> Linux 3.15-rc8 (2014-06-01 19:12:24 -0700)
>>>>>
>>>>
>>>> Did you rebase these? All the commits appear to be labeled with
>>>> today's date, and Chuck appears as the committer for all of them.
>>>>
>>>
>
> Shirley
>
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next prev parent reply other threads:[~2014-06-03 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 15:59 [GIT PULL] Please pull NFS client RDMA changes for 3.16 Anna Schumaker
2014-06-03 16:44 ` Trond Myklebust
2014-06-03 17:04 ` Anna Schumaker
2014-06-03 17:53 ` Trond Myklebust
2014-06-03 18:23 ` Shirley Ma
2014-06-03 23:07 ` Trond Myklebust [this message]
2014-06-04 1:17 ` Shirley Ma
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=CAHQdGtQdBjXCgQe62AV_Vm2uct9OtZw4t5AA3NKikA8_0rQ81A@mail.gmail.com \
--to=trond.myklebust@primarydata.com \
--cc=Anna.Schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=shirley.ma@oracle.com \
/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).