From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64506 invoked by alias); 5 Feb 2018 16:00:40 -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 64361 invoked by uid 89); 5 Feb 2018 16:00:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=conclusions X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-qt0-f178.google.com Received: from mail-qt0-f178.google.com (HELO mail-qt0-f178.google.com) (209.85.216.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 05 Feb 2018 16:00:38 +0000 Received: by mail-qt0-f178.google.com with SMTP id m11so12655872qtn.10; Mon, 05 Feb 2018 08:00:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=YVzgz+QC0xy7Pl2j0H0wMg1NbwU5QwOgo6CwBnQVPls=; b=mkjsWOnr5Mj5CHJe98nxPPyQnbsqFhNf5w/KwA2jUPK/siTroO+hgxYW6R4IAq69qm W7ZxOtswrsMC00qYtDHs2Uryq30STRQPLnZ7ZoeXqGUpGxv1sReBWjoxmkYGXQXshTIv TIFp7clNspCMcIbnBA5Nc56Xa8rEkR4U1f4elZGngrg+2CnpTAvAs6JUN+OJ8skaCQPg N0Vyqo4IIxxMsPqXlYF67tdwmnAfpZZOUTu1lR1quRw8HIVPmA4zX6A73ztzMVv8CWgd gw2LHb1Qy8QaP5EWfPP7Vw1FPm9ycnyDLi12vsVjyv8QIfLK5j3o6fG1//WokyHGb9i2 QGMw== X-Gm-Message-State: APf1xPBxFJsLIOUz+IJCB6iz9WMmP1OdTkRMsQlBAGfd+ZBy7B08WlGl 3KZx6uyg7Th/yhsX5/5sqZeoO7/roUjPaSWff4c= X-Google-Smtp-Source: AH8x226O6Rg2+GHw0SU0nP+si+X9DohPlwXca/SfHMbXygUjgkuSNvuoWJNlkomfi3IvjfRcKNuHL5v+uf+G+0jLlcg= X-Received: by 10.200.26.73 with SMTP id q9mr11235766qtk.174.1517846436452; Mon, 05 Feb 2018 08:00:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.153.232 with HTTP; Mon, 5 Feb 2018 08:00:36 -0800 (PST) From: Yao Qi Date: Mon, 05 Feb 2018 16:00:00 -0000 Message-ID: Subject: Stop updating ChangeLog? To: GDB , GDB Patches Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00065.txt.bz2 Hi all, The discussion in this thread https://sourceware.org/ml/gdb-patches/2018-02/msg00012.html leads to a discussion that whether we still need ChangeLog. I start a new thread to get more attention on this topic. In current development, we need to write one ore more changelog entries for each commit, put them into both git commit log and ChangeLog files. How much we can change to existing mode depends the answers to these following questions, #1 Are ChangeLog files useful in GDB releases to various people who build GDB releases? #2 Are ChangeLog files useful in GDB repo to various GDB developers? a) If answers are Yes/Yes, we keep unchanged, b) If answers are No/No, we don't need to write changelog entries in git commit log, nor updating ChangeLog file, c) If answer are Yes/No, developers still have to write changelog entries in git commit log, and we can generate ChangeLog on release from git log. d) If answers are No/Yes, get use to git to get the information from git log instead of ChangeLog, My answers are No/No, so I suggest that we do b). I can live up with c), but that needs change in the release process. What do you think? --=20 Yao (=E9=BD=90=E5=B0=A7) P.S. I found that this topic has been discussed several times in various projects (binutils, glibc, etc) without any conclusions. I do hope we can make some progress this time :)