From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id DB2873851C04 for ; Mon, 28 Dec 2020 23:54:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DB2873851C04 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gerald@pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 575F833E6E for ; Mon, 28 Dec 2020 18:54:58 -0500 (EST) Received: from [192.168.1.5] (77.118.226.34.wireless.dyn.drei.com [77.118.226.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id D143F33E6D for ; Mon, 28 Dec 2020 18:54:57 -0500 (EST) Date: Tue, 29 Dec 2020 00:54:53 +0100 (CET) From: Gerald Pfeifer To: gcc@gcc.gnu.org Subject: More consistency for Git log messages? Message-ID: <43eb3d64-2d5d-cbc9-3e3e-e06eedc2704b@pfeifer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Dec 2020 23:55:00 -0000 Having spent a bit more time with GCC sources (as opposed to wwwdocs) recently and looking for prior art to guide me, I noticed there's a lot of options to specific the ChangeLog file(s) to use. And correspondingly a lot of inconsistency. Right now we seem to allow for 1. gcc/cp/ChangeLog 2. gcc/cp/ChangeLog: 3. gcc/cp 4. gcc/cp: 5. gcc/cp/ and probably more. Can we streamline this a bit and converge on one of the forms 3-5? Personally I'd suggest 3 (the shortest) or 5 (the directory), but whatever ... as long as things become more consistent, which is easier on newbies and reading logs (or automatically processing them later on). Gerald