From: "Tobin C. Harding" <me@tobin.cc>
To: Linux docs <linux-doc@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Dan Williams <dan.j.williams@intel.com>,
"Tobin C. Harding" <me@tobin.cc>,
linux-kernel@vger.kernel.org
Subject: Maintainer docs for patch merging
Date: Wed, 20 Dec 2017 11:25:41 +1100 [thread overview]
Message-ID: <20171220002541.GW19604@eros> (raw)
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.
No rush on this, I know Christmas is soon.
thanks,
Tobin.
next reply other threads:[~2017-12-20 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 0:25 Tobin C. Harding [this message]
2017-12-20 7:56 ` Maintainer docs for patch merging Greg Kroah-Hartman
2017-12-20 10:13 ` Tobin C. Harding
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=20171220002541.GW19604@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