public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, gcc@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: gcc/DATESTAMP not updated any longer
Date: Fri, 11 Dec 2020 19:04:28 +0100	[thread overview]
Message-ID: <dca6af0f-c8db-a9ec-34bf-6107e8d8f848@suse.cz> (raw)
In-Reply-To: <ydd5z5832j5.fsf@CeBiTec.Uni-Bielefeld.DE>

On 12/11/20 2:17 PM, Rainer Orth wrote:
> Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> 
>> I noticed that gcc/DATESTAMP isn't updated any longer after this
>> Friday.  I doubt this is intentional...
> 
> This has happened again tonight...
> 
> 	Rainer
> 

Thanks for heads up. I'm aware of it and I don't see reason why (running the
update script in dry mode works).

@Jakub: Can you please take a look?

Thanks,
Martin

  reply	other threads:[~2020-12-11 18:04 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 [this message]
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
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=dca6af0f-c8db-a9ec-34bf-6107e8d8f848@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).