From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4gNcmV3sdpz2ynX for ; Sun, 24 May 2026 11:51:22 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4gNcmR1VPkz2xJ5 for ; Sun, 24 May 2026 11:51:19 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4gNcmN54hZz30M; Sun, 24 May 2026 11:51:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1779623476; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vkZSyUlUnRQzZTF2COczAkbvmHiBFHKMt8qpLW9eGNU=; b=E1u3kqePCdXTSKu/00Swu5jF4XTEPe2UEYmm9XoQ/m/t/5dN4Uh6o0oHhPNup8a4Uyj0Da BswL8wWY6wONUpeOI306HKly5+KNrvPUd0OGojxLhWRTQymNGTPT3YUY4tj0nRx7yWFAxo X5Y2zFnFdbi8oxX7Sf0r5OaH4p98D54W9IY0GRJgeOgyjNoWO9TTorDIC5EWg2rS/BHgpi 4XNsHVIAijlGs7RjG5nyvE9rPEOMrSSLYClFZT6cl0/qv/yJQunIDsQfpWaYtN/YVYJqxQ XhzwdqTcH7+y1RVkLngsF6DBtBuJ78LlDPQwfOMOPzlNXVnJ4iHxKBGQV0ggfw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1779623476; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vkZSyUlUnRQzZTF2COczAkbvmHiBFHKMt8qpLW9eGNU=; b=yrJ1up4Tdz20VlMHetz4BTrwJdLbyk/x6kMBNJt017HSep9SlvSqm8TMirp6rvG2/BA73D 9LhpeGaiTJh7UBBg== Message-ID: <6d1299c5-b7c2-4a13-bfa5-2d1a4d9b4183@ipfire.org> Date: Sun, 24 May 2026 13:51:16 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: GIT-Question: how do I start a commit with some explanations/comments Content-Language: en-US To: development@lists.ipfire.org References: <5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org> <3e28cb8a-16af-4ca7-8221-95fb6b56b041@ipfire.org> Cc: "IPFire: Belka, Adolf" From: Matthias Fischer In-Reply-To: <3e28cb8a-16af-4ca7-8221-95fb6b56b041@ipfire.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 . 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