[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171220075603.GA22932@kroah.com>
Date: Wed, 20 Dec 2017 08:56:03 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Tobin C. Harding" <me@...in.cc>
Cc: Linux docs <linux-doc@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Dan Williams <dan.j.williams@...el.com>,
linux-kernel@...r.kernel.org
Subject: Re: Maintainer docs for patch merging
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
> kernel.org 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...
thanks,
greg k-h
Powered by blists - more mailing lists