From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <segher@kernel.crashing.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
 by sourceware.org (Postfix) with ESMTP id 7442C395C41A;
 Thu, 23 Apr 2020 20:32:07 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7442C395C41A
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])
 by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 03NKW1Ra001493;
 Thu, 23 Apr 2020 15:32:01 -0500
Received: (from segher@localhost)
 by gate.crashing.org (8.14.1/8.14.1/Submit) id 03NKW1vQ001492;
 Thu, 23 Apr 2020 15:32:01 -0500
X-Authentication-Warning: gate.crashing.org: segher set sender to
 segher@kernel.crashing.org using -f
Date: Thu, 23 Apr 2020 15:32:00 -0500
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jeff Law <law@redhat.com>, Tamar Christina <Tamar.Christina@arm.com>,
 "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
 Jonathan Wakely via Gcc <gcc@gcc.gnu.org>,
 Overseers mailing list <overseers@sourceware.org>,
 Alexander Monakov <amonakov@ispras.ru>,
 "Frank Ch. Eigler" <fche@elastic.org>,
 Florian Weimer <fw@deneb.enyo.de>, Tom Tromey <tom@tromey.com>
Subject: Re: Not usable email content encoding
Message-ID: <20200423203200.GS26902@gate.crashing.org>
References: <CAFyWVaZfY-CfXwsTwrF8LduSBMYdFecD3x7MLP0ZYb8pC5qZPA@mail.gmail.com>
 <CAH6eHdQe5PdRe42BFeN4e9Ms9jy5Lb2R==FxENbD1TWnefnekA@mail.gmail.com>
 <87zhccsdfd.fsf@tromey.com> <87imj0pjbr.fsf@mid.deneb.enyo.de>
 <CAFiYyc1q6wBHOfCu2tuPj+bXCQyLfmve0iACVYZghve2GMfoaQ@mail.gmail.com>
 <87blosphsw.fsf@mid.deneb.enyo.de>
 <PR2PR08MB47473ECD0B20FFC0D2EF576BFFD30@PR2PR08MB4747.eurprd08.prod.outlook.com>
 <20200423114627.GG26902@gate.crashing.org>
 <bff45aa0a9a4867ef191ff6c6ead00208369acd3.camel@redhat.com>
 <20200423165743.GA27372@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200423165743.GA27372@redhat.com>
User-Agent: Mutt/1.4.2.3i
X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, TXREP, T_SPF_HELO_PERMERROR,
 T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 20:32:08 -0000

Hi!

On Thu, Apr 23, 2020 at 12:57:43PM -0400, Frank Ch. Eigler wrote:
> > *Nothing* should touch changelog files :-)  They should be generated from the
> > VCS.  IMHO of course.
> 
> IMHO: the VCS should be the changelog.

The VCS shows what changed.  The changelog shows what was meant to be
changed.  The difference is very helpful for reviewers, and for
post-mortem purposes, etc.

This can be more than compensated for if submitters would write better
patch descriptions, of course.  But will that happen?


Segher