From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 668383858D1E; Fri, 1 Sep 2023 20:43:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 668383858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693601000; bh=g9OI0TxyUEPITU+EtU+hEtpp4deHyK86VnFlkbbVTIY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wwcesMis7YrgWoVLSRqWeXMegEi6rfGQYTFIMTZIPcuw2LBmWxkPfDL+Yk+KsP2wu LRXHtk7SKJ8re+uwWmWBq6WC/+OXcFDvrm8RUCDSEHrZ6q3e2LIxkDDKZVoloHl+Rt DpMS6GQ5HcrD0Kbq0q9lCSdFzapGfdtlpRbjLRSw= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyB0YXJnZXQvMTExMjcwXSBnY2MvY29uZmlnL2kzODYvaTM4?= =?UTF-8?B?Ni1vcHRpb25zLmNjOjMwMzk6ODogd2FybmluZzogZHVwbGljYXRlZCDigJhp?= =?UTF-8?B?ZiDigJkgY29uZGl0aW9uIFstV2R1cGxpY2F0ZWQtY29uZF0=?= Date: Fri, 01 Sep 2023 20:43:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111270 --- Comment #2 from Jonathan Wakely --- This is nothing to do with me, g:d4ba3b369 doesn't touch that file at all, = and git blame doesn't show that commit for me. Do you have a shallow clone mayb= e, and d4ba3b369 is simply the first commit in your history?=