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 4gNZPF0wQPz30Lj for ; Sun, 24 May 2026 10:04:33 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (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 4gNZP95yZbz2xJ5 for ; Sun, 24 May 2026 10:04:29 +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 4gNZP84TcHz4c; Sun, 24 May 2026 10:04:28 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1779617068; 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=l0aHMVq5D5Xqg49FiVeaemT4J+L3yKWg5jYE9ujp27w=; b=AHwbb6pUvzZtnYPHrpDdXxAIc3959OZUoNaOKrdZv27nNps/anTJYqjASYZK+OuJCTuP4J H8Wb+dGn5FfAN7BA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1779617068; 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=l0aHMVq5D5Xqg49FiVeaemT4J+L3yKWg5jYE9ujp27w=; b=BMtFwn2b0enF3usYVA98vlaoACuDqOXfbTDFgOPfwic+ZAjKU+5m+7czlO7ANq5yl/sGrb cwsi8D/zpkrbFx8oRHEAXIzA7oVY7YIdCmvDJMBFPRBVa2vvV/Tf7B5InJ/9d7Y32l82lu uo3jrZ2g5477RmYHcbh/kqLLEUkkX2i76dzhR2xX25zgKQn5/XRZSDN9QDa52NqTDa0QNs zaBgH26UadwfffwwFSWK74Lq4MXr1rzbxeUngvtaQFPnK1WWxZx1Gh+ZkJ2neDCxQnV1pZ gdhl1VupC5+SlkfGrOkQu52tFzR/Ea54wbLK9k96JtwIPMKXpBjlFqkS7Uxzig== Message-ID: <3e28cb8a-16af-4ca7-8221-95fb6b56b041@ipfire.org> Date: Sun, 24 May 2026 12:04:25 +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 To: Matthias Fischer References: <5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org> Content-Language: en-GB Cc: development@lists.ipfire.org From: Adolf Belka In-Reply-To: <5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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'! ;-) >