public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
* GIT-Question: how do I start a commit with some explanations/comments
@ 2026-05-24  8:57 Matthias Fischer
  2026-05-24 10:04 ` Adolf Belka
  0 siblings, 1 reply; 3+ messages in thread
From: Matthias Fischer @ 2026-05-24  8:57 UTC (permalink / raw)
  To: IPFire: Development-List

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'! ;-)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: GIT-Question: how do I start a commit with some explanations/comments
  2026-05-24  8:57 GIT-Question: how do I start a commit with some explanations/comments Matthias Fischer
@ 2026-05-24 10:04 ` Adolf Belka
  2026-05-24 11:51   ` Matthias Fischer
  0 siblings, 1 reply; 3+ messages in thread
From: Adolf Belka @ 2026-05-24 10:04 UTC (permalink / raw)
  To: Matthias Fischer; +Cc: development

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.

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.

Regards,

Adolf.

> 
> 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'! ;-)
> 



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: GIT-Question: how do I start a commit with some explanations/comments
  2026-05-24 10:04 ` Adolf Belka
@ 2026-05-24 11:51   ` Matthias Fischer
  0 siblings, 0 replies; 3+ messages in thread
From: Matthias Fischer @ 2026-05-24 11:51 UTC (permalink / raw)
  To: development; +Cc: IPFire: Belka, Adolf

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-05-24 11:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-05-24  8:57 GIT-Question: how do I start a commit with some explanations/comments Matthias Fischer
2026-05-24 10:04 ` Adolf Belka
2026-05-24 11:51   ` Matthias Fischer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox