Maintainer docs for patch merging
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.
Quoted 13 lines · Tobin C. Harding
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?
Quoted 5 lines
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 :)
Quoted 1 line
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
Quoted 20 lines · Greg Kroah-Hartman
Quoted 13 lines · Tobin C. Harding
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?
Quoted 5 lines
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.
Quoted 7 lines
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 :)
Quoted 1 line
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.