SubmittingPatches: discuss subsystems separately from git.git
The discussion around subsystems disrupts the flow of discussion in the surrounding area, which only deals with starting points used for the git.git project. So move this bullet point out to the end. Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Linus Arver committed
Jul 14, 2023 at 06:01 UTC
3423e372e4021b6608d4b5e65da9231425d0c455
1 file changed
+4
-4
Documentation/SubmittingPatches
+4
-4
@@ -35,14 +35,14 @@ change is relevant to.
35
to stabilize, you would have to rebase it (see the "depends on other
36
topics" above).
37
38
-* Some parts of the system have dedicated maintainers with their own
39
- repositories (see the section "Subsystems" below). Changes to
40
- these parts should be based on their trees.
41
-
38
To find the tip of a topic branch, run `git log --first-parent
39
master..seen` and look for the merge commit. The second parent of this
40
commit is the tip of the topic branch.
41
42
+Finally, note that some parts of the system have dedicated maintainers
43
+with their own separate source code repositories (see the section
44
+"Subsystems" below).
45
+
46
[[separate-commits]]
47
=== Make separate commits for logically separate changes.
48