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

Re: [PATCH gitk] gitk: add README.md with contribution guidelines

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 20, 2025, 21:15 UTC
Message-ID
<xmqqfrdl8zjm.fsf@gitster.g>
In-Reply-To
<70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 10 quoted lines
>> It would be really nice if you add "review them here before you run
>> send-email" step between these two commands ;-).
>
> I alwyays use
>
>     git format-patch ... -opatchez
>     cat patchez/* | less
>
> Because sending out something weird to a mailing list gives me the
> chills.  (And there might be format-patch bugs.)
Thanks for a tip.

It matches what I do, except that I use ./+jc/<topic-name>/ directories as the staging area, as I tend to keep what I sent out for a few days, and I strongly prefer to give its own directory to each topic, to avoid "git send-email *.patch" sending out random unrelated patches.

Previous: Kristoffer HaugsbakkNext: Johannes Sixt
Message 8 of 9 in “gitk: add README.md with contribution guidelines”
  1. gitk: add README.md with contribution guidelinesMichael Rappazzo, Aug 20, 2025
  2. Junio C HamanoAug 20, 2025
  3. Mike RappazzoAug 20, 2025
  4. Junio C HamanoAug 20, 2025
  5. Mike RappazzoAug 20, 2025
  6. D. Ben KnobleAug 20, 2025
  7. Kristoffer HaugsbakkAug 20, 2025
  8. Junio C HamanoAug 20, 2025
  9. Johannes SixtAug 21, 2025

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.