From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id BFZoHQlBZWAqHwAAWB0awg (envelope-from ) for ; Wed, 31 Mar 2021 23:42:01 -0400 Received: by simark.ca (Postfix, from userid 112) id 68BA21EE1B; Wed, 31 Mar 2021 23:42:01 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 C31C01EE0E for ; Wed, 31 Mar 2021 23:41:59 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id DBE573858C27; Thu, 1 Apr 2021 03:41:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DBE573858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1617248518; bh=8hHiwlAJVPPtu16wmvhdYzGt9uoxLT/9YcKeFnvh2Bs=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=cC233tQWRadJVuzW9t++nM9RVfiaP5gbL/O1fkR6Wq24YCWsFL8FFEq4WD15MfO9r 9mVomuAfoaYWY+vghk1B0Bc3UPJ/aC9r46wEsmB653SvNUU90eQ8sUOZeDcvO4PBb3 UF1ZzVz3EAgsNeKMejklLtoPfRdsfBnu7a1dHaLI= Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) by sourceware.org (Postfix) with ESMTP id 8F4A53858C27 for ; Thu, 1 Apr 2021 03:41:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8F4A53858C27 Received: from vapier (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 98D0933B864; Thu, 1 Apr 2021 03:41:53 +0000 (UTC) Date: Wed, 31 Mar 2021 23:41:52 -0400 To: Joel Brobecker Subject: Re: sim: replacing ChangeLog files with online git logs Message-ID: Mail-Followup-To: Joel Brobecker , gdb@sourceware.org References: <83tup9disi.fsf@gnu.org> <20210323110638.GA6592@embecosm.com> <83wntwjy8h.fsf@gnu.org> <20210324165918.GA1683671@embecosm.com> <83lfacjvsj.fsf@gnu.org> <20210331032728.GJ11111@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210331032728.GJ11111@adacore.com> 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: Mike Frysinger via Gdb Reply-To: Mike Frysinger Cc: gdb@sourceware.org Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" On 31 Mar 2021 07:27, Joel Brobecker wrote: > > > > > No the second proposes to replace the current ChangeLog with one > > > > > auto-generated upon release. > > > > > > > > > > This ChangeLog would in effect be a reformatted `git log` output. > > > > > > > > I don't object to that, either. The question is: what we will require > > > > the Git log messages to contain then? Currently, the entire ChangeLog > > > > entry goes there, but once the manually written ChangeLog files are > > > > retired, what will remain? That was the crux of the recent > > > > discussion. > > > > > > we won't require the ChangeLog-like entries in the commit message for sim/. > > > the generated ChangeLog will have name+date+git log. > > > > i wanted to give time for people to respond & post any thoughts that they > > might have lingering before i moved forward. since things have gone quiet > > now, i guess we've reached the end? so i'll give another few days before > > i land the change for sim/. > > Can you hold off on this for now? We're discussing it within the group > of GDB Global Maintainers, and we need more time to converge. certainly. i just didn't want this to go dead for another 2 years before restarting the whole thing from scratch. manually writing ChangeLog entries anywhere is an incredible waste of my time. -mike