From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-il1-x143.google.com (mail-il1-x143.google.com [IPv6:2607:f8b0:4864:20::143]) by sourceware.org (Postfix) with ESMTPS id B2E9D3851C12; Wed, 27 May 2020 15:11:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B2E9D3851C12 Received: by mail-il1-x143.google.com with SMTP id v11so6972585ilh.1; Wed, 27 May 2020 08:11:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wxmln1+/9TmTjqWV3lazhDhOO+2T9v8msRmxygJ8rPc=; b=h0JL8CveP4uSZTpPISt95W4GQrFJmQwTRWOVnaQhDtrL1ElSNNRsEg8cCeDXO5JhIw qJfhHHlbFspuh+4iZrGLWIDhMWF1MPLfjNwOawEL2nJSMu5VnL3/1EhHn6M+isCd52bF r2bTCgOA1uad0/i7EKJpWjAbsSDazNcAju0exJJK4rSR/PLKKf7ZBKunsrwK/iqq8FLp hVz+EM+pSwOA5voKAxhPoi88vXc95zFcCypePswNbWDTPa4EMVM5LtcO9y7f+2yFXKUD 3FsSqHH/b20kjH7cycQ/i3zXMueqxmYdB0kPXdqT9zTmKyB/HxOBFczBxSLdLuEdcvMj DdRQ== X-Gm-Message-State: AOAM533dRemBRq8+wJ2Slc38YBxx8U/fXJhazMsQYnvEUqwiT3Ta0I7d l1ZnDs4zO5J0OO2JHJkgu444KTajg28GQL/5gEXnAQ== X-Google-Smtp-Source: ABdhPJzaZzhzZyaiOrjWo1APPQ1T17i23T3+sSC3lkYrQisnPNUWK+5XWM684l3bmvx1MnTwaTn8Oo5szOs+X4VkUg4= X-Received: by 2002:a92:d147:: with SMTP id t7mr3272815ilg.151.1590592282976; Wed, 27 May 2020 08:11:22 -0700 (PDT) MIME-Version: 1.0 References: <891ef86a-a47f-18f2-c6bd-e525719e3768@simark.ca> <9492d857-c259-1429-f1c7-31a6dbf6510f@simark.ca> In-Reply-To: <9492d857-c259-1429-f1c7-31a6dbf6510f@simark.ca> From: "H.J. Lu" Date: Wed, 27 May 2020 08:10:47 -0700 Message-ID: Subject: Auto update ChangeLog for binutils+gdb commits? To: Simon Marchi Cc: Binutils , GDB Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 15:11:25 -0000 On Wed, May 27, 2020 at 7:29 AM Simon Marchi wrote: > > On 2020-05-27 10:20 a.m., H.J. Lu wrote: > > On Wed, May 27, 2020 at 7:10 AM Simon Marchi wrote: > >> > >> On 2020-05-26 1:07 p.m., H.J. Lu via Gdb wrote: > >>> Hi, > >>> > >>> I had an impression that ChangeLog was auto generated for GDB commits. > >>> If it is true, should we do the same for binutils commits? > >>> > >>> -- > >>> H.J. > >>> > >> > >> No we (GDB) don't do that. There was a discussion here > >> > >> https://sourceware.org/pipermail/gdb-patches/2020-February/165728.html > >> > >> But it didn't go anywhere. Note that when I actually tried the script, it > >> didn't produce good results (perhaps because it wasn't designed with C++ > >> in mind). > > > > GCC will auto generate ChangeLog entry from git commit message. Can > > binutils+gdb do the same? > > Can you please explain what this means? I suspect that we are not talking about > the same thing. You mean, still write the ChangeLog entry by hand, but only put > it in the git commit. And then a script scrapes all the commit messages in order > to produce a ChangeLog file? > Yes. I updated the email subject. Personally, I think it is a good exercise to document what changes are in ChangeLog format in commit message. But adding them to ChangeLog files is a problem. If git commit hooks can do it automatically, it will be very nice. GCC will do it now. Can we do the same? -- H.J.