On Fri, 25 Sep 2026 13:00:47 +0100, Matthias Goergens <[email protected]> wrote: > > A git T: entry can name a branch after the repository URL. The first > to do so, commit a1aa5a770dc3 ("MAINTAINERS: update hwmon subsystem > git trees"), added two T: lines for one repository, one per branch. > Today 109 of the 846 git T: lines name a branch, and ten entries list > one repository more than once with different branches. Commit > 083bf9c56d06 ("get_maintainer: add more --self-test options") taught > get_maintainer.pl to check the branch with git ls-remote. Neither the > MAINTAINERS preamble nor submitting-patches.rst mentions any of this. > > Document the syntax only. What a named branch is for varies: many > entries name the branch linux-next merges, others a fixes or topic > branch, and some subsystems want patches based on a mainline tag rather > than on any branch of their tree. maintainer-entry-profile.rst already > asks a profile to say which branches go into linux-next and which one > contributors should submit against, so point there. > > In submitting-patches.rst, say that fixes for the current release cycle > and new development usually start from different places, and where to > find out which. > > Suggested-by: Theodore Ts'o <[email protected]> > Link: https://lore.kernel.org/all/[email protected]/ > Signed-off-by: Matthias Goergens <[email protected]>
Acked-by: Marc Zyngier <[email protected]> M. -- Jazz isn't dead. It just smells funny.
