public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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: Sun, 24 May 2026 13:51:16 +0200	[thread overview]
Message-ID: <6d1299c5-b7c2-4a13-bfa5-2d1a4d9b4183@ipfire.org> (raw)
In-Reply-To: <3e28cb8a-16af-4ca7-8221-95fb6b56b041@ipfire.org>

On 24.05.2026 12:04, Adolf Belka wrote:
> Hi Matthias,
> 
> On 24/05/2026 10:57, Matthias Fischer wrote:
>> 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 ...'.
> 
> When I have needed to do that I have added --cover-letter to my git format-patch -N -o ....
> command and it has then created a series patch with the N commits and added a cover letter at series number 0 which it then allows you to edit and add your message for the patch series.

Thanks Adolf! - in fact, I never used 'git format-patch' before, will
take a look at it.

> https://git-scm.com/docs/git-format-patch#Documentation/git-format-patch.txt---cover-letter
> 
> I have to say it is a long time now since I did this so you might have to try it a few times to get the patch series you want before running the git send-email command.

We'll see. I'm curious what will come out <G>. I just began reading the
'format-patch'-manual. DOH! How on earth did he program this!? ;-)

BTW:
Compiling, building and installing 'squid 7.5' on Core 201 was no
problem - its now running '--without-kettle' without any seen problems
or errors. Base was the lfs I sent yesterday.

Next plan is to edit 'proxy.cgi' and to remove the unneeded parts of the
code bit by bit. I'll keep the list informed... ;-)

Best
Matthias



  reply	other threads:[~2026-05-24 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 [this message]
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=6d1299c5-b7c2-4a13-bfa5-2d1a4d9b4183@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