From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26025 invoked by alias); 13 Feb 2020 02:29:43 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 25163 invoked by uid 89); 13 Feb 2020 02:29:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=blessed X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (207.211.31.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 13 Feb 2020 02:29:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581560979; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rRjeIhh1IO1kWlcM0UNkcF5GJmRMmOMhGg2n7Lrb94w=; b=FspVHuikfLRIz5yf1fRJjqQWWuV8A3iwM0xSLwSlS4FJMEJSNxPihSB3JdDsRDnpDJeGO2 bf0J6qzmppl8nwCyZBkutyHvCHTWv0ALFRQ8lCDqpje3TVKvUP7FvfL4DoN/9hbLDRn/Tn 0pWpHLywx3g9r3LTB9qJW/cuf38JQVY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-393-PXjfuJcuPSWMhdRCVPBeHw-1; Wed, 12 Feb 2020 21:29:34 -0500 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6CF341851FC2; Thu, 13 Feb 2020 02:29:33 +0000 (UTC) Received: from ovpn-116-60.phx2.redhat.com (ovpn-116-60.phx2.redhat.com [10.3.116.60]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1CB0B90083; Thu, 13 Feb 2020 02:29:33 +0000 (UTC) Message-ID: <97220aed713c824cecd34a5eceee1af3b63ebd18.camel@redhat.com> Subject: Re: Using the vcs_to_changelog.py script From: Jeff Law Reply-To: law@redhat.com To: Alan Modra , Simon Marchi Cc: binutils@sourceware.org, "gdb-patches@sourceware.org" Date: Thu, 13 Feb 2020 02:29:00 -0000 In-Reply-To: <20200213010322.GB29647@bubble.grove.modra.org> References: <20200213010322.GB29647@bubble.grove.modra.org> User-Agent: Evolution 3.34.3 (3.34.3-1.fc31) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00234.txt.bz2 On Thu, 2020-02-13 at 11:33 +1030, Alan Modra wrote: > On Wed, Feb 12, 2020 at 06:32:51PM -0500, Simon Marchi wrote: > > For illustrative purposes, here's what the script outputs for the last bunch > > of commits in binutils-gdb: > > > > http://paste.ubuntu.com/p/x38zs82Rmt/ > > Not fit for the original purpose of change logs as far as developers > are concerned, but I for one don't use them at all nowadays to see > what changed when. "git log" and "git blame" are far better. I'm in a similar position. For years ChangeLogs were my go-to for initial archaeology, but I find myself using git log and git blame most of the time now. > > Does this satisfy the FSF legal requirements? "Who changed what" > won't be accurate unless committers remember to set the author > properly on commits made for other people. RMS and/or the FSF blessed it for glibc a while back. So it'd seem suitable for other projects under the FSF umbrella. I'm hoping we'll make the same change for GCC, but there's some inertia to push through :( jeff