public inbox for gccadmin@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Pinski <apinski@qti.qualcomm.com>
Cc: "Andrew Pinski (QUIC)" <quic_apinski@quicinc.com>,
"Arsen Arsenović" <arsen@aarsen.me>,
"David Malcolm" <dmalcolm@redhat.com>,
"Feng Wang" <wangfeng@eswincomputing.com>,
"GCC Administrator" <gccadmin@gcc.gnu.org>,
"Harald Anlauf" <anlauf@gmx.de>,
"Jakub Jelinek" <jakub@redhat.com>,
Juzhe-Zhong <juzhe.zhong@rivai.ai>,
"Ken Matsui" <kmatsui@gcc.gnu.org>,
"Kito Cheng" <kito.cheng@sifive.com>,
"Kuan-Lin Chen" <rufus@andestech.com>,
"Kwok Cheung Yeung" <kcy@codesourcery.com>,
"Li Wei" <liwei@loongson.cn>, "Pan Li" <pan2.li@intel.com>,
"Patrick Palka" <ppalka@redhat.com>,
"Raiki Tamura" <tamaron1203@gmail.com>,
"Roger Sayle" <roger@nextmovesoftware.com>,
"Sandra Loosemore" <sandra@codesourcery.com>,
"YunQiang Su" <syq@gcc.gnu.org>,
chenxiaolong <ch.enxiaolong@loongson.cn>,
"gcc-testresults@gcc.gnu.org" <gcc-testresults@gcc.gnu.org>
Subject: Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
Date: Sat, 6 Jan 2024 01:28:11 +0100 [thread overview]
Message-ID: <20240106002811.GR26453@gnu.wildebeest.org> (raw)
In-Reply-To: <DM6PR02MB4058681D0C260770132136EC95662@DM6PR02MB4058.namprd02.prod.outlook.com>
Hi,
On Fri, Jan 05, 2024 at 03:49:59AM +0000, Andrew Pinski wrote:
> This is just a copyright year difference for Makefile.in . Looks
> like Makefile.am was updated with the new year but Makefile.in was
> not regenerated/updated in some cases.
Yeah, seems like not all generated files were regenerated after the
copyright year update. The last remaining diff is just libgomp/configure.
I'll commit that regeneration as obvious.
Cheers,
Mark
next prev parent reply other threads:[~2024-01-06 0:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 2:30 builder
2024-01-05 3:49 ` Andrew Pinski
2024-01-06 0:28 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 18:59 builder
2024-04-12 5:14 builder
2024-04-11 10:34 builder
2024-04-11 10:34 builder
2024-04-11 1:17 builder
2024-04-10 17:21 builder
2024-04-09 17:23 builder
2024-04-09 7:54 builder
2024-04-09 7:48 builder
2024-04-09 3:16 builder
2024-04-05 9:48 builder
2024-04-03 12:43 builder
2024-04-01 1:44 builder
2024-01-05 20:59 builder
2024-01-05 20:58 builder
2024-01-04 1:34 builder
2023-12-01 7:14 builder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240106002811.GR26453@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=anlauf@gmx.de \
--cc=apinski@qti.qualcomm.com \
--cc=arsen@aarsen.me \
--cc=ch.enxiaolong@loongson.cn \
--cc=dmalcolm@redhat.com \
--cc=gcc-testresults@gcc.gnu.org \
--cc=gccadmin@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kcy@codesourcery.com \
--cc=kito.cheng@sifive.com \
--cc=kmatsui@gcc.gnu.org \
--cc=liwei@loongson.cn \
--cc=pan2.li@intel.com \
--cc=ppalka@redhat.com \
--cc=quic_apinski@quicinc.com \
--cc=roger@nextmovesoftware.com \
--cc=rufus@andestech.com \
--cc=sandra@codesourcery.com \
--cc=syq@gcc.gnu.org \
--cc=tamaron1203@gmail.com \
--cc=wangfeng@eswincomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).