lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 3 Nov 2011 09:08:18 +0100
From:	Christoph Biedl <linux-kernel.bfrz@...chmal.in-ulm.de>
To:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [068/107] Update email address for stable patch submission

Greg KH wrote...

(...)

Just out of curiosity:

>   - Send the patch, after verifying that it follows the above rules, to
> -   stable@...r.kernel.org.
> +   stable@...r.kernel.org.
>   - The sender will receive an ACK when the patch has been accepted into the

>     other developers and by the relevant subsystem maintainer.
> - - If the stable@...r.kernel.org address is added to a patch, when it goes into
> + - If the stable@...r.kernel.org address is added to a patch, when it goes into
>     Linus's tree it will automatically be emailed to the stable team.

Whatever you used to create the patches, why did these hunks come into
existence?

    Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ