From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56494 invoked by alias); 13 Feb 2020 03:37:43 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 56474 invoked by uid 89); 13 Feb 2020 03:37:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=our X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 13 Feb 2020 03:37:41 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:49289) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j25Jp-0007yg-PF; Wed, 12 Feb 2020 22:37:37 -0500 Received: from [176.228.60.248] (port=2447 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1j25Jp-0004f2-3t; Wed, 12 Feb 2020 22:37:37 -0500 Date: Thu, 13 Feb 2020 03:37:00 -0000 Message-Id: <83imkbqhry.fsf@gnu.org> From: Eli Zaretskii To: Simon Marchi CC: binutils@sourceware.org, gdb-patches@sourceware.org In-reply-to: (message from Simon Marchi on Wed, 12 Feb 2020 18:32:51 -0500) Subject: Re: Using the vcs_to_changelog.py script References: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00486.txt.bz2 > From: Simon Marchi > Date: Wed, 12 Feb 2020 18:32:51 -0500 > > 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. Several things we'd need to consider if we go this way: . AFAIK, the script you mention currently supports only C sources; we'd need to see how well it supports C++ . Some files in our tree are neither C++ nor C: there are Python files, Guile files, shell scripts, and Texinfo files, to mention just a few: what to do about them? . Last, but not least: we'd need detailed instructions for how to produce the commit log messages under this regime, because the old conventions will not be valid anymore.