From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id wE4tLadmf2ZfaAEAe85BDQ:P1 (envelope-from ) for ; Sat, 29 Jun 2024 01:43:04 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id wE4tLadmf2ZfaAEAe85BDQ (envelope-from ) for ; Sat, 29 Jun 2024 03:43:03 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=mCLsGmyP; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1719625383; h=from:from:sender:sender: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:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=21XB/tHi5p75pwHFjWjClWmeFeXyruhoRBTHRD0g2NY=; b=sB5JgVKP1hT/rxYR2pUxyi5TSZP09aHTUSUvDLBemrl3q4fobGoIRfgfaBRwYCw6Jv+rmR k0NC1AD7MYCE9hlNmJYuGt4wLjVTf5Vvm/P7SmvAXk7e0ydlOQVWdyo3PgjwMYC1VRZ7BJ i8daVuvbFBEHTJBiir+Eka8UtssmwA+uAZbjVCRTQ7sCpHzmHgjPLrL/LR2FUdrvhr52YN rXHM12XRQhnRE0gPmrfSaf/fcG6sLkXNInlYjDS9S0vrkALYZ7wXxNdUvyjZL0GVuVt4Xi Cd8bdSRvoPuJSVQNddxYpgGQjdlbUWLR7vNsKEYbCCMIWqgGOcg52qNYpED6bA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=mCLsGmyP; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1719625383; a=rsa-sha256; cv=none; b=XVwd15TfF12DqYTmF5xyvGrhan+JHA5Nx37qu9GMMPyuPMIT01bpwg6aGGPOKiJiVgmZTY IoR9S8xGWzi+iGgHxDQxbCTcxPbW7iYI2x0C7WaSY04KZilYLvU7GcIVmjTfV276KEERcB qc8l2xp4ir9byqZoOZdIZNRC2uuS1E2asyuRhryFeYAji0YIGmlrW9lrMI+JEOcHIeJIpm aRGCp4iQqPGF5KwcITru7fjO3N/SQW6Znlqbd3VWi+EPCEGJ6qcpSSSM+APgxEp6beH3me WZigG/6gXZWIQ4V6wb8+OSIQaFZZBHJPirKnA1Hkqxo18HnOuGGLV4YtZHYpXA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id CE271AD12 for ; Sat, 29 Jun 2024 03:43:02 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sNN6b-0008WB-Gg; Fri, 28 Jun 2024 21:42:21 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sNN6a-0008VU-Ob for guix-devel@gnu.org; Fri, 28 Jun 2024 21:42:20 -0400 Received: from mail-108-mta246.mxroute.com ([136.175.108.246]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sNN6Y-0007wo-Ny for guix-devel@gnu.org; Fri, 28 Jun 2024 21:42:20 -0400 Received: from filter006.mxroute.com ([136.175.111.3] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta246.mxroute.com (ZoneMTA) with ESMTPSA id 19061a8448e00017a3.002 for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Sat, 29 Jun 2024 01:42:15 +0000 X-Zone-Loop: c71d7153198fc1cba5429d73e4d114735775998e1e5c X-Originating-IP: [136.175.111.3] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=freakingpenguin.com; s=x; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=21XB/tHi5p75pwHFjWjClWmeFeXyruhoRBTHRD0g2NY=; b=mCLsGmyPHYHUCDxRid80ihQ+wi AxZpjuQ21nPCN8Cr2wTg8WZKYDvQRJHGEK/PgYq9u8vXGQqcTVjkwuAAtTbXS6kY9kIRpNvrYS+P8 SA1dWCu/0jljIHZAsPMKzUojUoFVngUVbT1ZviZ5mNRzedSuv6qkhW9uuBe2TS3yiW8FHFVfB5WJC vVkIkcwFa6zhxpxgUrmGxR4peAzCfu2KIS1LbRjsf+tv9dSD47cY/T+01bvFptTM+mTZ0LlYXtWp8 btawj1J98ZgkfpH6Enf5xvT2rpjGMyzCa+KHv8LochMeYpL+y0FAMOXK8HpGLBaJemqZ/cx7ZH8qO xVJxmBZw==; From: Richard Sent To: Maxim Cournoyer Cc: guix-devel@gnu.org Subject: Re: Codifying/Documenting Guix commit message conventions? In-Reply-To: <877ce8a6yh.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 28 Jun 2024 21:11:34 -0400") References: <87bk3mvvfy.fsf@freakingpenguin.com> <877ce8a6yh.fsf@gmail.com> Date: Fri, 28 Jun 2024 21:42:12 -0400 Message-ID: <877ce8v823.fsf@freakingpenguin.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Id: richard@freakingpenguin.com Received-SPF: pass client-ip=136.175.108.246; envelope-from=richard@freakingpenguin.com; helo=mail-108-mta246.mxroute.com X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -5.38 X-Migadu-Queue-Id: CE271AD12 X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -5.38 X-TUID: 69gv5J9B16ET Hi Maxim, Thanks for the detailed response! (And Andreas as well) > Another Emacs tip for those who don't know it yet: pressing 'C' > (capital C) on a diff hunk while authoring a commit message using > Magit will create some ChangeLog entry stub in the commit message > buffer, which saves a lot of typing. Perhaps we should mention this in > our doc, as it makes writing GNU ChangeLog less painful. Bonus points, there's a magit-generate-changelog [1] function that can be run from the commit message buffer that'll insert changelog entries for every diff hunk. I use this snippet to bind it to the commit entry keymap: --8<---------------cut here---------------start------------->8--- (use-package magit ;; ... :bind (:map git-commit-mode-map ("C-c m" . magit-generate-changelog))) --8<---------------cut here---------------end--------------->8--- > That sounds like a good, incremental, non-controversial approach to the > issues found (good observation, by the way!); I encourage you to pursue > it. Got it, I'll take a crack at it at some point. I'll approach it from the perspective of documenting current practices (standardizing on one option when there are alternatives). Then if we don't like those practices ([] vs <>), we can discuss if we should push for matching GNU ChangeLog or leave it as is. The joys of Texinfo await me. For some values of joy. =F0=9F=99=82 (If I recall correctly there's been discussion of an RFC process in the past. I don't recall the details but depending on how expansive this becomes perhaps that's relevant.) [1]: https://github.com/magit/magit/pull/3928 --=20 Take it easy, Richard Sent Making my computer weirder one commit at a time.