linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Maintainer docs for patch merging
@ 2017-12-20  0:25 Tobin C. Harding
  2017-12-20  7:56 ` Greg Kroah-Hartman
  0 siblings, 1 reply; 3+ messages in thread
From: Tobin C. Harding @ 2017-12-20  0:25 UTC (permalink / raw)
  To: Linux docs
  Cc: Greg Kroah-Hartman, Andrew Morton, Jonathan Corbet, Dan Williams,
	Tobin C. Harding, linux-kernel

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Maintainer docs for patch merging
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Greg Kroah-Hartman @ 2017-12-20  7:56 UTC (permalink / raw)
  To: Tobin C. Harding
  Cc: Linux docs, Andrew Morton, Jonathan Corbet, Dan Williams,
	linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Maintainer docs for patch merging
  2017-12-20  7:56 ` Greg Kroah-Hartman
@ 2017-12-20 10:13   ` Tobin C. Harding
  0 siblings, 0 replies; 3+ messages in thread
From: Tobin C. Harding @ 2017-12-20 10:13 UTC (permalink / raw)
  To: Greg Kroah-Hartman
  Cc: Linux docs, Andrew Morton, Jonathan Corbet, Dan Williams,
	linux-kernel

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-12-20 10:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).