git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/3] SubmittingPatches: mention subsystems with dedicated repositories

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 1, 2013, 23:24 UTC
Message-ID
<1357082695-29713-3-git-send-email-gitster@pobox.com>
In-Reply-To
<1357082695-29713-1-git-send-email-gitster@pobox.com>

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>
---
 Documentation/SubmittingPatches | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index b9fd182..e810263 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -88,6 +88,10 @@ change is relevant to.
    wait until some of the dependent topics graduate to 'master', and
    rebase your work.
 
+ - 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..pu" and look for the merge commit. The second parent of this
 commit is the tip of the topic branch.
@@ -279,6 +283,26 @@ You can also create your own tag or use one that's in common usage
 such as "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:".
 
 ------------------------------------------------
+Subsystems with dedicated maintainers
+
+Some parts of the system have dedicated maintainers with their own
+repositories.
+
+ - git-gui/ comes from git-gui project, maintained by Pat Thoyts:
+
+        git://repo.or.cz/git-gui.git
+
+ - gitk-git/ comes from Paul Mackerras's gitk project:
+
+        git://ozlabs.org/~paulus/gitk
+
+ - po/ comes from the localization coordinator, Jiang Xin:
+
+	https://github.com/git-l10n/git-po/
+
+Patches to these parts should be based on their trees.
+
+------------------------------------------------
 An ideal patch flow
 
 Here is an ideal patch flow for this project the current maintainer
-- 
1.8.1.209.gc32ab23
Previous: Junio C HamanoNext: Jason Holden
Message 3 of 12 in “Update SubmittingPatches”
  1. 0/3 Update SubmittingPatchesJunio C Hamano, Jan 1, 2013
  2. 1/3 SubmittingPatches: who am I and who cares?Junio C Hamano, Jan 1, 2013
  3. 2/3 SubmittingPatches: mention subsystems with dedicated repositoriesJunio C Hamano, Jan 1, 2013
  4. Jason HoldenJan 2, 2013
  5. Junio C HamanoJan 2, 2013
  6. Junio C HamanoJan 2, 2013
  7. SubmittingPatches: Document how to request a patch review tagJason Holden, Jan 4, 2013
  8. Junio C HamanoJan 4, 2013
  9. Michael HaggertyJan 6, 2013
  10. Junio C HamanoJan 6, 2013
  11. 3/3 SubmittingPatches: remove overlong checklistJunio C Hamano, Jan 1, 2013
  12. Jeff KingJan 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.