From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33987 invoked by alias); 12 Feb 2020 23:33:03 -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 33855 invoked by uid 89); 12 Feb 2020 23:33:02 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=illustrative, UD:ca, our X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 12 Feb 2020 23:33:00 +0000 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 01CNWqR6021637 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Feb 2020 18:32:57 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 01CNWqR6021637 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=polymtl.ca; s=default; t=1581550378; bh=TpHYY4v9GABIajIIWdOZ7GiWPsRcqtuJfW2X5Vh5QEM=; h=To:From:Subject:Date:From; b=ASst9GSCMvF3fF1AdUhT8FtckqFoOEsLFfFFffaMJi/ka4EC/MWWR7uUWss529qBP E7Zt225Fm59ds8NoXcF48WE7Zzhj2D85WdtGPIfrg+vr2o7gx8zaY4VvbITaTSu5FE G09SSHQ26XtWmBnlFJLX/WafOhHdEHY02uaTQuYQ= Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (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 8097B1E10B; Wed, 12 Feb 2020 18:32:52 -0500 (EST) To: binutils@sourceware.org, "gdb-patches@sourceware.org" From: Simon Marchi Subject: Using the vcs_to_changelog.py script Message-ID: Date: Wed, 12 Feb 2020 23:33:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg00231.txt.bz2 Hi binutils and gdb folks! As you may or may not know, the glibc project has started using a script called vcs_to_changelog.py to automatically generate their ChangeLogs. They don't do hand-written ChangeLog entries with their contributions. Instead they generate a ChangeLog file using that script when creating a release, passing it a range of git commits for which to create ChangeLog entries. I would very much like if we started using this in GDB, and it was suggested that we could try to sync with binutils, as you might want to do the same. Here's how it could work in practice: 1. We update our gnulib import to import the vcs_to_changelog.py script (it is distributed as a gnulib module). 2. We update src-release.sh to call the script and generate a single top-level ChangeLog that is included in the release tarball. If we use the script as it is today, the ChangeLog generated for a binutils release will contain entries for commits that don't concern binutils (for example, that just touch a file under gdb/) and vice-versa. I don't think that's really a problem, since all the required information will be there, there will just be additional information (which I doubt anybody will care about). But if really needed, I'm sure the script could be modified to filter down the commits that touch only what's included in the binutils or GDB release (I would prefer to avoid doing this unless absolutely necessary). For illustrative purposes, here's what the script outputs for the last bunch of commits in binutils-gdb: http://paste.ubuntu.com/p/x38zs82Rmt/ That's it, please let me know what you think. Simon