diff mbox series

[3/5] SubmittingPatches: discuss subsystems separately from git.git

Message ID d430a4ed8ee9d5a3d45a3a2b373ed3377cf5fd62.1688778359.git.gitgitgadget@gmail.com (mailing list archive)
State Superseded
Headers show
Series SubmittingPatches: clarify which branch to use | expand

Commit Message

Linus Arver July 8, 2023, 1:05 a.m. UTC 
From: Linus Arver <linusa@google.com>

The discussion around subsystems disrupts the flow of discussion in the
surrounding area, which only deals with branches used for the git.git
project. So move this bullet point out to the end.

Signed-off-by: Linus Arver <linusa@google.com>
---
 Documentation/SubmittingPatches | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff mbox series

Patch

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 5611580fb4c..48918181f49 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -35,14 +35,14 @@  change is relevant to.
   to stabilize, you would have to rebase it (see the "depends on other
   topics" above).
 
-* Some parts of the system have dedicated maintainers with their own
-  repositories (see the section "Subsystems" below).  Changes to
-  these parts should be based on their trees.
-
 To find the tip of a topic branch, run `git log --first-parent
 master..seen` and look for the merge commit. The second parent of this
 commit is the tip of the topic branch.
 
+Note that some parts of the system have dedicated maintainers with their
+own separate source code repositories (see the section "Subsystems"
+below).
+
 [[separate-commits]]
 === Make separate commits for logically separate changes.