From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: bad commits in the nfs tree
Date: Wed, 4 Jun 2014 08:38:57 -0400 [thread overview]
Message-ID: <538F1361.6060400@netapp.com> (raw)
In-Reply-To: <CAABAsM4hpz_vCK=AbLUzBnVCr3-_5KhJUqif3YP3Yjp+-ojx8w@mail.gmail.com>
On 06/03/2014 06:46 PM, Trond Myklebust wrote:
> On Tue, Jun 3, 2014 at 6:34 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi Trond,
>>
>> I noticed in the nfs tree this morning 2 commits that have been
>> cherry-picked from Linus' tree:
>>
>> cc6d854967ce Linux 3.15-rc8
>> 2b267bb3a8e5 powerpc: Wire renameat2() syscall
>>
>> These are part of a branch that you merged from Anna Schumaker. It
>> looks like they may have been included when Anna was trying to rebase
>> the rest of the branch onto v3.15-rc8?
>>
>> Please fix this up before asking Linus to pull your tree.
>>
>
> Thanks Stephen! We're still ironing out the kinks in a new process for
> the NFS client maintenance, and appreciate your patience.
>
> Anna, let's avoid the mess that is 3.15-rc8 for now. Please rebase on
> top of commit b5968725f46d (Push the file layout driver into a
> subdirectory) from my nfs-for-next branch and retag the resulting
> branch using the same commit information as earlier.
> I'll pull the new tag once you send the word that all is ready...
Sure. I'll take care of that right away!
Anna
>
> Thanks
> Trond
>
WARNING: multiple messages have this Message-ID (diff)
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: bad commits in the nfs tree
Date: Wed, 4 Jun 2014 08:38:57 -0400 [thread overview]
Message-ID: <538F1361.6060400@netapp.com> (raw)
In-Reply-To: <CAABAsM4hpz_vCK=AbLUzBnVCr3-_5KhJUqif3YP3Yjp+-ojx8w@mail.gmail.com>
On 06/03/2014 06:46 PM, Trond Myklebust wrote:
> On Tue, Jun 3, 2014 at 6:34 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi Trond,
>>
>> I noticed in the nfs tree this morning 2 commits that have been
>> cherry-picked from Linus' tree:
>>
>> cc6d854967ce Linux 3.15-rc8
>> 2b267bb3a8e5 powerpc: Wire renameat2() syscall
>>
>> These are part of a branch that you merged from Anna Schumaker. It
>> looks like they may have been included when Anna was trying to rebase
>> the rest of the branch onto v3.15-rc8?
>>
>> Please fix this up before asking Linus to pull your tree.
>>
>
> Thanks Stephen! We're still ironing out the kinks in a new process for
> the NFS client maintenance, and appreciate your patience.
>
> Anna, let's avoid the mess that is 3.15-rc8 for now. Please rebase on
> top of commit b5968725f46d (Push the file layout driver into a
> subdirectory) from my nfs-for-next branch and retag the resulting
> branch using the same commit information as earlier.
> I'll pull the new tag once you send the word that all is ready...
Sure. I'll take care of that right away!
Anna
>
> Thanks
> Trond
>
next prev parent reply other threads:[~2014-06-04 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:34 linux-next: bad commits in the nfs tree Stephen Rothwell
2014-06-03 22:46 ` Trond Myklebust
2014-06-04 12:38 ` Anna Schumaker [this message]
2014-06-04 12:38 ` Anna Schumaker
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=538F1361.6060400@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@fys.uio.no \
/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.