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

Re: [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 30, 2012, 20:26 UTC
Message-ID
<7va9svffr4.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1356891535-5647-1-git-send-email-jason.k.holden.swdev@gmail.com>
Jason Holden <jason.k.holden.swdev@gmail.com> writes:
> I spent a good amount of time yesterday figuring out the correct workflow
> to submit a change to gitk.

Thanks; I just realized that nothing in Documentation/ hierarchy mentions these; they are only mentioned in "A Note from the Maintainer" I send out every once in a while (kept in MaintNotes of 'todo' branch):

    * Other people's trees, trusted lieutenants and credits.
    Documentation/SubmittingPatches outlines to whom your proposed changes
    should be sent.  As described in contrib/README, I would delegate fixes
    and enhancements in contrib/ area to the primary contributors of them.
    Although the following are included in git.git repository, they have their
    own authoritative repository and maintainers:
     - 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/
Perhaps the update should mention po/ as well?
Previous: Jason HoldenNext: Thomas Ackermann
Message 4 of 7 in “Add MAINTAINERS file and clarify gui workflows”
  1. 0/2 Add MAINTAINERS file and clarify gui workflowsJason Holden, Dec 30, 2012
  2. 1/2 Add top-level maintainers file with email/canonical repository informationJason Holden, Dec 30, 2012
  3. 2/2 Provide better guidance for submitting patches against git-gui, gitkJason Holden, Dec 30, 2012
  4. Junio C HamanoDec 30, 2012
  5. Thomas AckermannDec 31, 2012
  6. Jason HoldenDec 31, 2012
  7. Junio C HamanoDec 31, 2012

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.