From: Junio C Hamano <gitster@pobox.com>
To: Michael Rappazzo <rappazzo@gmail.com>
Cc: git@vger.kernel.org, j6t@kdbg.org
Subject: Re: [PATCH gitk] gitk: add README.md with contribution guidelines
Date: Wed, 20 Aug 2025 13:57:48 -0700 [thread overview]
Message-ID: <xmqq349laeyb.fsf@gitster.g> (raw)
In-Reply-To: <20250820195229.45943-1-rappazzo@gmail.com> (Michael Rappazzo's message of "Wed, 20 Aug 2025 15:52:29 -0400")
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 ;-).
Thanks.
next prev parent reply other threads:[~2025-08-20 20:57 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 [this message]
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
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=xmqq349laeyb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=rappazzo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).