From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id TcImI0eE/F+VHgAAWB0awg (envelope-from ) for ; Mon, 11 Jan 2021 12:00:55 -0500 Received: by simark.ca (Postfix, from userid 112) id 842531EEEF; Mon, 11 Jan 2021 12:00:55 -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 1D3751E4F4 for ; Mon, 11 Jan 2021 12:00:55 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C7136383F85E; Mon, 11 Jan 2021 17:00:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7136383F85E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1610384454; bh=/vlNbCMQD+6VQjFbw3qOnniDzZmNxX9oGiJo1Wf7t2s=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=yHmQvt9pt+9OLTzRehSbRGUXPBduOypfwPjRj85tuR9tJb7kkGrA/dR+AcBZH55Sv iZocfS+g8dxqiSDa1XHtLINElNTqLleIC5DreZdt7XmnoudruG9XAZZabMH9Kpl+Ej +jjxvVUq1vA9hd6yx5Sk24aFSyHanbgZgymPNOBI= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id C2803386184F for ; Mon, 11 Jan 2021 17:00:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C2803386184F Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 10BH0cR8000454 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 11 Jan 2021 12:00:43 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 10BH0cR8000454 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 47EF21E4F4; Mon, 11 Jan 2021 12:00:38 -0500 (EST) Subject: Re: [PATCH] sim: switch to autogenerated ChangeLog files To: Andrew Burgess , Mike Frysinger References: <20210110033752.6002-1-vapier@gentoo.org> <20210110034223.6268-1-vapier@gentoo.org> <20210111110544.GC1151657@embecosm.com> Message-ID: <313988fb-ed42-11f7-1e64-b46005580792@polymtl.ca> Date: Mon, 11 Jan 2021 12:00:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210111110544.GC1151657@embecosm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 11 Jan 2021 17:00:38 +0000 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: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" 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. Last time I tried the gitlog-to-changelog script on GDB, it produced horrible results. Probably because it was not designed for C++. 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. 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. Simon