From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>,
"Michael Rappazzo" <rappazzo@gmail•com>
Cc: git@vger•kernel.org, "Johannes Sixt" <j6t@kdbg•org>
Subject: Re: [PATCH gitk] gitk: add README.md with contribution guidelines
Date: Wed, 20 Aug 2025 23:03:45 +0200 [thread overview]
Message-ID: <70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com> (raw)
In-Reply-To: <xmqq349laeyb.fsf@gitster.g>
On Wed, Aug 20, 2025, at 22:57, Junio C Hamano wrote:
> Michael Rappazzo <rappazzo@gmail•com> writes:
>
>> +#### Creating and Sending Patches
>> +After committing your changes:
>> +```bash
>> +git format-patch -1 --subject-prefix="PATCH gitk"
>> +git send-email --to=git@vger•kernel.org --cc=j6t@kdbg•org *.patch
>> +```
>
> Just being curious, but does the project strongly discourage a
> multi-patch topic?
>
> 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.)
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2025-08-20 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 19:52 [PATCH gitk] gitk: add README.md with contribution guidelines Michael Rappazzo
2025-08-20 20:57 ` Junio C Hamano
2025-08-20 21:02 ` Mike Rappazzo
2025-08-20 21:12 ` Junio C Hamano
2025-08-20 21:20 ` Mike Rappazzo
2025-08-20 23:42 ` D. Ben Knoble
2025-08-20 21:03 ` Kristoffer Haugsbakk [this message]
2025-08-20 21:15 ` Junio C Hamano
2025-08-21 7:15 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=j6t@kdbg$(echo .)org \
--cc=rappazzo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox