SubmittingPatches: mention subsystems with dedicated repositories
These were only mentioned in periodical "A note from the maintainer" posting and not in the documentation suite. SubmittingPatches has a section to help contributors decide on what commit to base their changes, which is the most suitable place for this information. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jan 1, 2013 at 14:37 UTC
e6da8ee8d84fe0ea6dc99ac625d7e0e07246f39d
1 file changed
+24
Documentation/SubmittingPatches
+24
@@ -88,6 +88,10 @@ change is relevant to.
88
wait until some of the dependent topics graduate to 'master', and
89
rebase your work.
90
91
+ - Some parts of the system have dedicated maintainers with their own
92
+ repositories (see the section "Subsystems" below). Changes to
93
+ these parts should be based on their trees.
94
+
95
To find the tip of a topic branch, run "git log --first-parent
96
master..pu" and look for the merge commit. The second parent of this
97
commit is the tip of the topic branch.
@@ -278,6 +282,26 @@ If you like, you can put extra tags at the end:
282
You can also create your own tag or use one that's in common usage
283
such as "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:".
284
285
+------------------------------------------------
286
+Subsystems with dedicated maintainers
287
+
288
+Some parts of the system have dedicated maintainers with their own
289
+repositories.
290
+
291
+ - git-gui/ comes from git-gui project, maintained by Pat Thoyts:
292
+
293
+ git://repo.or.cz/git-gui.git
294
+
295
+ - gitk-git/ comes from Paul Mackerras's gitk project:
296
+
297
+ git://ozlabs.org/~paulus/gitk
298
+
299
+ - po/ comes from the localization coordinator, Jiang Xin:
300
+
301
+ https://github.com/git-l10n/git-po/
302
+
303
+Patches to these parts should be based on their trees.
304
+
305
------------------------------------------------
306
An ideal patch flow
307