From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: "IPFire: Belka, Adolf" <adolf.belka@ipfire.org>
Subject: Re: GIT-Question: how do I start a commit with some explanations/comments
Date: Tue, 16 Jun 2026 13:51:34 +0200 [thread overview]
Message-ID: <132c2642-b8b7-4c97-bc9a-4d9d0a24a244@ipfire.org> (raw)
In-Reply-To: <6d1299c5-b7c2-4a13-bfa5-2d1a4d9b4183@ipfire.org>
Hi Adolf,
On 24.05.2026 13:51, Matthias Fischer wrote:
> When I have needed to do that I have added --cover-letter to my git format-patch -N -o ....
I read some documentation (think of it!) and it was easier than I thought:
git send-email --annotate --smtp-domain=devel64-1.localdomain
--cover-letter -4
This did the job... ;-) Easy.
Best
Matthias
prev parent reply other threads:[~2026-06-16 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 8:57 Matthias Fischer
2026-05-24 10:04 ` Adolf Belka
2026-05-24 11:51 ` Matthias Fischer
2026-06-16 11:51 ` Matthias Fischer [this message]
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=132c2642-b8b7-4c97-bc9a-4d9d0a24a244@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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