A git T: entry in MAINTAINERS may name a branch after the repository URL, and where it does, that branch rather than the repository's HEAD is the one to prepare patches against. Say so where contributors are sent to the T: entry.
Suggested-by: Theodore Ts'o <[email protected]> Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Matthias Goergens <[email protected]> --- Documentation/process/submitting-patches.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index 7ae79452e1b4..2936388dcaee 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -37,8 +37,9 @@ which can be grabbed with:: Note, however, that you may not want to develop against the mainline tree directly. Most subsystem maintainers run their own trees and want to see patches prepared against those trees. See the **T:** entry for the subsystem -in the MAINTAINERS file to find that tree, or simply ask the maintainer if -the tree is not listed there. +in the MAINTAINERS file to find that tree, and the branch to work against if +the entry names one, or simply ask the maintainer if the tree is not listed +there. .. _describe_changes: -- 2.55.0
