From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id SUVeJz6p/F9SIwAAWB0awg (envelope-from ) for ; Mon, 11 Jan 2021 14:38:38 -0500 Received: by simark.ca (Postfix, from userid 112) id 9641E1EEEF; Mon, 11 Jan 2021 14:38:38 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (unknown [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 1D5A61E4F4 for ; Mon, 11 Jan 2021 14:38:38 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 44881384B406; Mon, 11 Jan 2021 19:38:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 44881384B406 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1610393917; bh=QouZf/XWRye+ykm64o2kjABkAqMsnEoAxZnzCh5pBws=; 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=bKgLyYK/JS+tc8f2W1dt1G2xUSSKspSJ+/lS/L+T0D9d6xTybWxAK2Nl4z4fez0kQ sm0HnlxYTSVlLjxceNzXIo9KQnK/sWAqLEteiJLkKi2dWPT6IJdzHmAsxrnxvTMW34 lNWdo9vYC7XWuOiPipeG7abgIAc5fuCIsFvcW5vE= Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 106353857C65 for ; Mon, 11 Jan 2021 19:38:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 106353857C65 Received: from vapier (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with SMTP id 3242B340FC2; Mon, 11 Jan 2021 19:38:32 +0000 (UTC) Date: Mon, 11 Jan 2021 14:38:30 -0500 To: Simon Marchi Subject: Re: [PATCH] sim: switch to autogenerated ChangeLog files Message-ID: <20210111193830.GT7494@vapier> Mail-Followup-To: Simon Marchi , Andrew Burgess , gdb-patches@sourceware.org References: <20210110033752.6002-1-vapier@gentoo.org> <20210110034223.6268-1-vapier@gentoo.org> <20210111110544.GC1151657@embecosm.com> <313988fb-ed42-11f7-1e64-b46005580792@polymtl.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HtRZva1Vzv8iP5ye" Content-Disposition: inline In-Reply-To: <313988fb-ed42-11f7-1e64-b46005580792@polymtl.ca> X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Mike Frysinger via Gdb-patches Reply-To: Mike Frysinger Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" --HtRZva1Vzv8iP5ye Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 11 Jan 2021 12:00, Simon Marchi wrote: > On 2021-01-11 6:05 a.m., Andrew Burgess wrote: > > I think sim/ should follow the same policy as gdb/ for now. Do feel > > free to raise this as a suggestion for gdb/ in general though, it > > would be an interesting conversation to observe. >=20 > Last time I tried the gitlog-to-changelog script on GDB, it produced > horrible results. Probably because it was not designed for C++. >=20 > Making a script to produce ChangeLogs for C code is already very > difficult, making it work with good results for C++ would be even > worst. And most importantly, I think it would be wasted development > time. to be clear, it isn't generating entries exactly like we write. it's using the git commit logs with formatted dates. so i don't think this applies exactly anymore. so it's inline with the GNU's VCS principles: https://www.gnu.org/prep/standards/html_node/Change-Logs.html (and that also recommends just using gitlog-to-changelog). > My opinion is that we should either keep hand-written ChangeLogs, or > admit that ChangeLogs are not useful and get rid of them altogether > (and you know which side I lean towards). But auto-generating > ChangeLogs, other than allowing to check the "we have ChangeLog" box, > doesn't produce anything useful. i'm obviously a huge +1 for this ;) -mike --HtRZva1Vzv8iP5ye Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAl/8qTYACgkQQWM7n+g3 9YEHZw//W57cyUnhfdTJaaUSyKviqp74sDjurPDuwiK8RGsHQcSaA8sRTvXp5vfm 5gV55t5OaFsUAcV7/044hskAgDHafK7S14A7ws5ScEkGpRNVFePUtscO2wXzkqRC xxLg/fhekujmxg1ME17aL+2wD0dqAcn5c+FIB+cYrbb9AnYLLcdIYtg3HwVSEK6x X5JOpbudzp/P4/Q+rMp5Xp95EmHXKmoMDYLl5Ugj785HUHy8vwGSKwR8R1Av2F3K 1SVosILSu4nBbFhZf4a7w3HtK93XyKzfMjoBT8hkVkuLdUEUNIoY33KXeFwprxus fWj0RV1lBn/MEuz+J9Idhg5PxDsUre8iNRHHJvnX5AtmByjHCQmkiC7WZ1BRgJXF TJSTQydT3XeZZ8s7GR4CW29ZMEXvxNwFRLoBieTxd4FeKr90Qo+xx8GdSrqymS/t aRe5PTgKbHgouFzJJtBxmtTKjDBMb8M8R377neTIvrrjvd1VZYzle9np94fpGund 2px5cAVEAYBZf+Co95srbixpsUcomQggEWFZc1ZxJhPB5kdzJWJO27jAMtC4moQl Jc6CIJ9OAqEwl0ofrMV8+7JGKkLVqDR22N6vvAeizZoAVGXek2Rt1M4KasCSzKDP tUNBQ3ZLkofj4NTUBFd67dZyFBUZuyq+VuZRAuCBjGM0yI7konQ= =0FlV -----END PGP SIGNATURE----- --HtRZva1Vzv8iP5ye--