From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by sourceware.org (Postfix) with ESMTP id 40719397306E for ; Fri, 1 May 2020 15:52:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 40719397306E Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-275-AKsm3FACPX6YvEpR6KUuew-1; Fri, 01 May 2020 11:51:59 -0400 X-MC-Unique: AKsm3FACPX6YvEpR6KUuew-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B358A100CC85; Fri, 1 May 2020 15:51:57 +0000 (UTC) Received: from ovpn-114-206.phx2.redhat.com (ovpn-114-206.phx2.redhat.com [10.3.114.206]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1ECF360C47; Fri, 1 May 2020 15:51:54 +0000 (UTC) Message-ID: Subject: Re: Not usable email content encoding From: Jeff Law Reply-To: law@redhat.com To: Tom Tromey , Segher Boessenkool Cc: Tamar Christina , "overseers@gcc.gnu.org" , Jonathan Wakely via Gcc , Overseers mailing list , Alexander Monakov , "Frank Ch. Eigler" , "Frank Ch. Eigler" , Florian Weimer Date: Fri, 01 May 2020 09:51:53 -0600 In-Reply-To: <87zhb1nbue.fsf@tromey.com> References: <87zhccsdfd.fsf@tromey.com> <87imj0pjbr.fsf@mid.deneb.enyo.de> <87blosphsw.fsf@mid.deneb.enyo.de> <20200423114627.GG26902@gate.crashing.org> <20200423202708.GR26902@gate.crashing.org> <87zhb1nbue.fsf@tromey.com> Organization: Red Hat User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=unavailable 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2020 15:52:05 -0000 On Thu, 2020-04-23 at 15:14 -0600, Tom Tromey wrote: > > > > > > "Segher" == Segher Boessenkool writes: > > Segher> My point was that this should *never* be part of patches, already. > > FWIW, I use a few scripts so that I can keep ChangeLogs as files. > That's what I do when working on gdb. > > https://github.com/tromey/git-gnu-changelog > > This is easier on the whole, IME, because it means there is no extra > manual step before pushing. Right. And that's really my goal here -- eliminate the manual steps. Ideally I want to be able to git am; git push on a good patch. Manual steps for good patches need to be excised from the workflow. The ChangeLog file is a major problem in that regard. > > Of course, better would be to remove ChangeLogs entirely (including not > putting anything like them into a commit message), because they are > largely not useful and are just make-work. Again IMNSHO -- I know there > are some folks who read them, but I basically never have since switching > to git. I read them less and less. At this point I think I read them to see if a particular patch in my queue has already been applied. Otherwise I'm using the git info. jeff