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 4gNXwR73bJz30Hc for ; Sun, 24 May 2026 08:57:59 +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 4gNXwN4jdGz2xLw for ; Sun, 24 May 2026 08:57:56 +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 4gNXwM2x5XzDg for ; Sun, 24 May 2026 08:57:55 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1779613075; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=WsJnnfi70wcIrqD9jVFSdts2EAoZERDk0qifglkePHI=; b=c136UtO9QsFmzMcdDAP1O15mTfxFccgrzF+A/RW7Z8Fk2OsvzEz8mgkRKosgyFyai1nvCw JdxS7lLmO6c5WkAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1779613075; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=WsJnnfi70wcIrqD9jVFSdts2EAoZERDk0qifglkePHI=; b=Ovcq9JVJCEgyx6AETKif2owE96pd8aH9VVzxqE7XpZoqRS0YNhoh0A86bHFdsx5bHv9VFS BfGmLGfTZXQuahZD8KlLgQGFZg+mNuh7AHqQu0Os4V4TrYXcTEQSdt4cyc/7JZtUmBLsC1 G5E7telNIPs6FAnMGIW433/XRsis1lvdpoduP+AzQ9XGhcOAOfh6OScbF+9P0U3N/eGkww BsfEfnYwRbHvqUyPaT5Gs/yfZbQErhcxp6WpixYtYJkXSNugCFJqpIw1I0rdCwmmYKMaOY IgpigS5RE9coxvjvVKieDVWu+kMZWLZFuavAWECjNUNnOdo8+B/EEmQrjzUTVw== Message-ID: <5d4f6ba5-f14c-4034-9a5d-5493a5d334d8@ipfire.org> Date: Sun, 24 May 2026 10:57:48 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-US To: "IPFire: Development-List" From: Matthias Fischer Subject: GIT-Question: how do I start a commit with some explanations/comments Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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'! ;-)