From: "Tobin C. Harding" <me@tobin.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux docs <linux-doc@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Maintainer docs for patch merging
Date: Wed, 20 Dec 2017 21:13:34 +1100 [thread overview]
Message-ID: <20171220101334.GC9037@eros> (raw)
In-Reply-To: <20171220075603.GA22932@kroah.com>
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
> > 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...
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.
thanks,
Tobin.
prev parent reply other threads:[~2017-12-20 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 0:25 Maintainer docs for patch merging Tobin C. Harding
2017-12-20 7:56 ` Greg Kroah-Hartman
2017-12-20 10:13 ` Tobin C. Harding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171220101334.GC9037@eros \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox