From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Jq1tBRQjUmCFBAAAWB0awg (envelope-from ) for ; Wed, 17 Mar 2021 11:41:08 -0400 Received: by simark.ca (Postfix, from userid 112) id 084291EF78; Wed, 17 Mar 2021 11:41:08 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (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 simark.ca (Postfix) with ESMTPS id 1ADBC1E789 for ; Wed, 17 Mar 2021 11:41:04 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 388EA385481A; Wed, 17 Mar 2021 15:41:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 388EA385481A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1615995663; bh=NlRKxNmmsGFycVJeHh5GtjOhEf858in2XZbipHUXb/Q=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=Mi5tiJtaF5O9X4TcIBfySBTAQCNVphwTJKNhLEKGozjzCPFkMAP/mX7JVbwgSg131 VUsAU0X8IoV4f5RwoV9gWzLhCpvX92cCeI744XxkxUKiv31s8M692FWlgUVEeUo/iU 8OQLvdS25uXd3L+TDYcBovm7lgss49LD26NIHVYg= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id E0BD8385481A for ; Wed, 17 Mar 2021 15:41:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E0BD8385481A Received: from fencepost.gnu.org ([2001:470:142:3::e]:38205) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMYI8-0001sy-Gb; Wed, 17 Mar 2021 11:41:00 -0400 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2188 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lMYI7-0007aS-F7; Wed, 17 Mar 2021 11:41:00 -0400 Date: Wed, 17 Mar 2021 17:40:56 +0200 Message-Id: <83mtv1dbzr.fsf@gnu.org> To: Luis Machado In-Reply-To: <18f4f0e2-0a35-a6c5-1886-943f81f817fd@linaro.org> (message from Luis Machado on Wed, 17 Mar 2021 12:22:46 -0300) Subject: Re: sim: replacing ChangeLog files with online git logs References: <83ft0zjys1.fsf@gnu.org> <83lfarhwjq.fsf@gnu.org> <83eegjhuuq.fsf@gnu.org> <8335wyj461.fsf@gnu.org> <83tup9disi.fsf@gnu.org> <2012fb21-38f2-3d1c-62c8-52d94d19e243@linaro.org> <83pmzxdegd.fsf@gnu.org> <83o8fhddg3.fsf@gnu.org> <18f4f0e2-0a35-a6c5-1886-943f81f817fd@linaro.org> X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb Reply-To: Eli Zaretskii Cc: gdb@sourceware.org Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" > Cc: vapier@gentoo.org, gdb@sourceware.org > From: Luis Machado > Date: Wed, 17 Mar 2021 12:22:46 -0300 > > Given the idea is to drop ChangeLog files for sim/ (for reasons Mike has > exposed), it would make no sense to keep embedding a manually-written > ChangeLog entry in the git commit message. So the only two sections left > in the commit message would be the subject line and the description. That doesn't have to be so, though. How to format the Git log messages when ChangeLog files are dropped is a separate discussion. > The list of changes would be auto-generated by a script, but it will > certainly be less descriptive than a manually-written ChangeLog entry. > It will only list things like "modified" or "new file". > > > > > For example, in Emacs we ask contributors to format the Git log > > messages according to ChangeLog format, and then the generated > > ChangeLog file looks exactly like the manual one would. > > > > I may be mistaken, but I think the idea is to drop ChangeLog > dependencies even from commit messages. That will simplify the > contribution process given ChangeLog files/entries will be > auto-generated by the mentioned script. The list of files touched by a changeset can be easily generated, but the functions/macros/classes not so easily, and not necessarily accurately enough, even if we will use the more elaborate script that is used by glibc. So some information loss will be present. OTOH, the ChangeLog-format Git log messages don't require one to have the ChangeLog file, they just require to use the same format when describing the changeset. If you use Emacs to make the changes themselves and commit the changes into Git, you just need to use the Emacs commands to format the Git log messages, those commands will produce the same information as the manual ChangeLog files automatically. If that is not an option that this community wants to adopt, then gitlog-to-changelog is probably not the adequate solution, and we should try using vcs-to-changelog.py (also in Gnulib).