On Thu, 2014-09-18 at 14:23 +0100, David Howells wrote:
> James Morris wrote:
>
> > > > No, if they go direct to Linus, they don't go into -next.
> > >
> > > Can you then sync your -next branch to Linus after Linus takes them
> > > please?
> >
> > Nope, I only want to sync on point releases u
James Morris wrote:
> > > No, if they go direct to Linus, they don't go into -next.
> >
> > Can you then sync your -next branch to Linus after Linus takes them please?
>
> Nope, I only want to sync on point releases unless absolutely necessary.
In that case, can you please just pull the reques
On Thu, 18 Sep 2014, David Howells wrote:
> James Morris wrote:
>
> > No, if they go direct to Linus, they don't go into -next.
>
> Can you then sync your -next branch to Linus after Linus takes them please?
Nope, I only want to sync on point releases unless absolutely necessary.
--
James M
James Morris wrote:
> No, if they go direct to Linus, they don't go into -next.
Can you then sync your -next branch to Linus after Linus takes them please?
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Tue, 16 Sep 2014, David Howells wrote:
> > Can you please pull these fixes and send them on upstream:
>
> Can you also pull them into your next branch as I have stuff for your next
> branch that depends on those changes?
No, if they go direct to Linus, they don't go into -next.
--
James Mo
Hi James,
Can you please pull these fixes and send them on upstream:
(1) Reinstate the production of EPERM for key types beginning with '.' in
requests from userspace.
(2) Tidy up the cleanup of PKCS#7 message signed information blocks and fix a
bug this made more obvious.
They will
David Howells wrote:
>
> Can you please pull these fixes and send them on upstream:
>
> (1) Reinstate the production of EPERM for key types beginning with '.' in
> requests from userspace.
>
> (2) Tidy up the cleanup of PKCS#7 message signed information blocks and fix a
> bug this
> Can you please pull these fixes and send them on upstream:
Can you also pull them into your next branch as I have stuff for your next
branch that depends on those changes?
Thanks,
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
Hi James,
Can you please pull these fixes and send them on upstream:
(1) Reinstate the production of EPERM for key types beginning with '.' in
requests from userspace.
(2) Tidy up the cleanup of PKCS#7 message signed information blocks and fix a
bug this made more obvious.
David
---
9 matches
Mail list logo