From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48935 invoked by alias); 25 Dec 2019 19:19:57 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 48926 invoked by uid 89); 25 Dec 2019 19:19:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=pin, CET, cet, Definitely X-HELO: snark.thyrsus.com Received: from thyrsus.com (HELO snark.thyrsus.com) (71.162.243.5) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Dec 2019 19:19:55 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 0B4D24704CB6; Wed, 25 Dec 2019 14:19:54 -0500 (EST) Date: Wed, 25 Dec 2019 19:19:00 -0000 From: "Eric S. Raymond" To: Andreas Schwab Cc: Roman Zhuykov , Segher Boessenkool , Joseph Myers , gcc@gcc.gnu.org, Alexander Monakov , Maxim Kuvyrkov Subject: Re: Test GCC conversion with reposurgeon available Message-ID: <20191225191954.GB19267@thyrsus.com> Reply-To: esr@thyrsus.com References: <28ca5dbe-a29e-7f1e-a599-d80709643421@ispras.ru> <20191224155543.GH4505@gate.crashing.org> <20191224181444.GJ4505@gate.crashing.org> <279bf8dd-8725-c3fa-0def-130b3d128509@ispras.ru> <871rssiigs.fsf@hase.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <871rssiigs.fsf@hase.home> User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00415.txt.bz2 Andreas Schwab : > Definitely not. I have never authored or committed any revision in the > -0800 time zone. That's easily fixed by adding a timezone entry to your author-map entry - CET, is it? That will prevent reposurgeon from making any attempt to deduce your timezone. It would be interesting to know how reposurgeon got misled. Most likely it was by a Changelog entry. Reposurgeon watches as these are being processed to see if it can pin an email address to a single timezone by looking up its TLD in the IANA database. I don't know how that could land you in California, though. Maybe I ought to be logging timezone deductions so we can trace them back. Has anyone else seen wrong timezone attributions? -- Eric S. Raymond