From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754343AbdLTH4D (ORCPT ); Wed, 20 Dec 2017 02:56:03 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:49044 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751384AbdLTH4B (ORCPT ); Wed, 20 Dec 2017 02:56:01 -0500 Date: Wed, 20 Dec 2017 08:56:03 +0100 From: Greg Kroah-Hartman To: "Tobin C. Harding" Cc: Linux docs , Andrew Morton , Jonathan Corbet , Dan Williams , linux-kernel@vger.kernel.org Subject: Re: Maintainer docs for patch merging Message-ID: <20171220075603.GA22932@kroah.com> References: <20171220002541.GW19604@eros> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171220002541.GW19604@eros> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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