From: Andreas Schwab <schwab@linux-m68k.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc@gcc.gnu.org
Subject: Re: gcc/DATESTAMP not updated any longer
Date: Mon, 14 Dec 2020 11:02:44 +0100 [thread overview]
Message-ID: <875z54ln7f.fsf@igel.home> (raw)
In-Reply-To: <5d853a91-75b3-6c8f-d60b-2d78cbee168d@suse.cz> ("Martin =?utf-8?Q?Li=C5=A1ka=22's?= message of "Mon, 14 Dec 2020 09:59:22 +0100")
On Dez 14 2020, Martin Liška wrote:
> On 12/11/20 7:26 PM, Jakub Jelinek wrote:
>> When running it manually it just completed without problems.
>> So, no idea what happened.
>
> Morning.
>
> Unfortunately, today we have similar problem. Master was bumped, but
> not any of the release branches:
Perhaps it was competing with an ongoing push?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-12-14 10:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:14 Rainer Orth
2020-11-02 19:43 ` Jakub Jelinek
2020-11-02 20:37 ` Martin Liška
2020-11-02 20:58 ` Jakub Jelinek
2020-11-03 18:26 ` Joseph Myers
2020-11-06 19:45 ` Jakub Jelinek
2020-11-06 19:56 ` Richard Biener
2020-11-06 19:59 ` Jakub Jelinek
2020-11-06 20:08 ` Iain Sandoe
2020-11-08 9:55 ` Iain Sandoe
2020-11-09 7:57 ` Martin Liška
2020-11-09 22:09 ` Jakub Jelinek
2020-11-10 8:23 ` Martin Liška
2020-11-13 9:57 ` Jakub Jelinek
2020-12-11 13:17 ` Rainer Orth
2020-12-11 18:04 ` Martin Liška
2020-12-11 18:26 ` Jakub Jelinek
2020-12-14 8:59 ` Martin Liška
2020-12-14 9:05 ` Jakub Jelinek
2020-12-14 9:21 ` Martin Liška
2020-12-14 9:23 ` Jakub Jelinek
2020-12-14 9:32 ` Martin Liška
2020-12-14 10:02 ` Andreas Schwab [this message]
2020-12-14 10:18 ` Jakub Jelinek
2020-12-15 0:04 ` Joseph Myers
2020-12-14 23:58 ` Joseph Myers
2020-12-15 8:30 ` Martin Liška
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=875z54ln7f.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mliska@suse.cz \
/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).