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

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

From
JHJason Holden <jason.k.holden.swdev@gmail.com>
Date
Dec 30, 2012, 18:18 UTC
Message-ID
<1356891535-5647-1-git-send-email-jason.k.holden.swdev@gmail.com>

I spent a good amount of time yesterday figuring out the correct workflow to submit a change to gitk. As I understand it, gitk (and I think git-gui) are maintained upstream of git, and patches should be sent to the git email list against the upstream repo. I think a top-level MAINTAINERS file would help new contributers like me get orientated, especially in the cases of these upstream projects that require a somewhat non-standard workflow

I also added some additional clarifications to SubmittingPatches that clarifies the additional steps required to submit patches against the guis.

Please double check that I've got the correct email addresses and canonical repositories

I'm guessing there are additional Maintainers who should be added to the MAINTAINERS file, I just haven't followed to email list closely enough to know all the formal/informal workflows that should be observed.

Jason Holden (2):
  Add top-level maintainers file with email/canonical repository
    information
  Provide better guidance for submitting patches against git-gui, gitk
 Documentation/SubmittingPatches | 11 +++++++++++
 MAINTAINERS                     | 17 +++++++++++++++++
 2 files changed, 28 insertions(+)
 create mode 100644 MAINTAINERS
-- 
1.8.1.rc3.28.g0ab5d1f
Next: Jason Holden
Message 1 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.