public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/1] Test of new GCC GNATS db.
Date: Wed, 01 Apr 2020 00:18:15 +0000	[thread overview]
Message-ID: <bug-1-4-JNVmrWEhlj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-1-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by GCC Administrator
<gccadmin@gcc.gnu.org>:

https://gcc.gnu.org/g:2594e9a069698d99ac5a012f3189288e19a5094b

commit r9-8428-g2594e9a069698d99ac5a012f3189288e19a5094b
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Wed Apr 1 00:17:49 2020 +0000

    Daily bump.

  parent reply	other threads:[~2020-04-01  0:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1-4@http.gcc.gnu.org/bugzilla/>
2020-04-01  0:17 ` cvs-commit at gcc dot gnu.org
2020-04-01  0:17 ` cvs-commit at gcc dot gnu.org
2020-04-01  0:18 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-01  7:37 ` cvs-commit at gcc dot gnu.org
2020-04-01  7:45 ` cvs-commit at gcc dot gnu.org
2020-04-01  9:58 ` cvs-commit at gcc dot gnu.org
     [not found] <bug-1-3646@http.gcc.gnu.org/bugzilla/>
2005-12-15 19:52 ` bryce at gcc dot gnu dot org
2005-12-15 20:04 ` bryce at gcc dot gnu dot org
2005-12-15 22:38 ` jsm28 at gcc dot gnu dot org
2006-01-18 23:53 ` dharinih at yahoo dot com
2006-01-19  0:15 ` pinskia at gcc dot gnu dot org
2006-01-28 21:17 ` pinskia at gcc dot gnu dot org
     [not found] <19990803195600.1.crash@cygnus.com>
2003-07-02  9:36 ` cvs-commit at gcc dot gnu dot org

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=bug-1-4-JNVmrWEhlj@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).