From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753944AbdLTAZu (ORCPT ); Tue, 19 Dec 2017 19:25:50 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:38279 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753439AbdLTAZp (ORCPT ); Tue, 19 Dec 2017 19:25:45 -0500 X-ME-Sender: Date: Wed, 20 Dec 2017 11:25:41 +1100 From: "Tobin C. Harding" To: Linux docs Cc: Greg Kroah-Hartman , Andrew Morton , Jonathan Corbet , Dan Williams , "Tobin C. Harding" , linux-kernel@vger.kernel.org Subject: Maintainer docs for patch merging Message-ID: <20171220002541.GW19604@eros> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.5.24 (2015-08-30) User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.