All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Michael Rappazzo" <rappazzo@gmail.com>,
	 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 14:15:57 -0700	[thread overview]
Message-ID: <xmqqfrdl8zjm.fsf@gitster.g> (raw)
In-Reply-To: <70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 20 Aug 2025 23:03:45 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

>> 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.

  reply	other threads:[~2025-08-20 21:16 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
2025-08-20 21:15     ` Junio C Hamano [this message]
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=xmqqfrdl8zjm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.