From: Matthias Fischer <matthias.fischer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: GIT-Question: how do I start a commit with some explanations/comments
Date: Sun, 24 May 2026 10:57:48 +0200 [thread overview]
Message-ID: <5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org> (raw)
Hi,
I'd like to have a problem but I can't find the solution...
Problem:
How do I create a commit that starts with a comment on the commits that
will follow immediately afterward? In other words, the first commit
(numbered 1/2, e.g.) should be a detailed comment, and the actual patch
(2/2, e.g.) should then follow as a *second* commit.
It might have something to do with 'git commit ...'.
I saw this here - first came a commit containing some explanations and
comments, then came the actual patch, but I can't figure it out.
Any help or a hint would be appreciated, 'git commit -- help' didn't
help... ;-)
Best
Matthias
P.S.: And I *don't* mean 'git commit --amend'! ;-)
next reply other threads:[~2026-05-24 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 8:57 Matthias Fischer [this message]
2026-05-24 10:04 ` Adolf Belka
2026-05-24 11:51 ` Matthias Fischer
2026-06-16 11:51 ` Matthias Fischer
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=5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org \
--to=matthias.fischer@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