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] [day] [month] [year] [list]
Date:   Wed, 20 Dec 2017 21:13:34 +1100
From:   "Tobin C. Harding" <>
To:     Greg Kroah-Hartman <>
Cc:     Linux docs <>,
        Andrew Morton <>,
        Jonathan Corbet <>,
        Dan Williams <>,
Subject: Re: Maintainer docs for patch merging

On Wed, Dec 20, 2017 at 08:56:03AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Dec 20, 2017 at 11:25:41AM +1100, Tobin C. Harding wrote:
> > Hi,
> > 
> > Recently we started a maintainer book (merged into Jonathan's docs-next
> > branch).
> > 
> > Would any current maintainers please be willing to explain how they go
> > about generating the automated emails one often receives when a patch
> > [set] is applied.
> > 
> > This may also be related to tree/branch management for maintainers
> > shows some people like to use multiple trees and some use
> > branches? 
> > 
> > If deemed relevant we could add a section to the new book (and I'd also
> > like to know how to do it for my own tree please so I can copy ;)
> > 
> > I have CC'd Greg and Andrew because they seem to have a system in place
> > for this.
> I "stole" Andrew's scripts for this a long time ago.  I guess I can
> write up something "real" for the documentation so that others can see
> the shell mess that drives those emails :)
> > No rush on this, I know Christmas is soon.
> Yeah, this will have to wait until mid January at the earliest...

Cool, thanks. Don't stress, I can give you a friendly reminder after LCA
(end of Jan) if you like save you wasting memory on it.


Powered by blists - more mailing lists