lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 18 Sep 2014 09:43:21 -0400
From:	Mimi Zohar <>
To:	David Howells <>
Cc:	James Morris <>,,,
Subject: Re: [Keyrings] [GIT PULL] KEYS: Fixes for keyrings

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 unless absolutely necessary.
> In that case, can you please just pull the request in this message that I sent
> you:
> 	[GIT PULL] KEYS: Changes for keyrings for security/next
> It has the aforementioned fixes and the stuff for -next both.  If you can just
> pull the lot into your -next branch rather than sending the fixes upstream at
> this point.

David, consider copying stable to automatically have bug fixes
backported.  After your "signed-off-by" add "Cc:
<>  <release>" to indicate which kernel release.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists