public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: write2mark1@gmail.com
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug regression/103997] [12 Regression] gcc.target/i386/pr88531-??.c scan-assembler-times FAILs
Date: Sat, 29 Jan 2022 14:40:20 -0800	[thread overview]
Message-ID: <CAE5rLuLkPp6u3FNBdGTJhDFqvyYeF1yVp3xeJ0kRz=xVQgJVvQ@mail.gmail.com> (raw)
In-Reply-To: <bug-103997-4-UCKcgObNTC@http.gcc.gnu.org/bugzilla/>

Why does gcc use CVS and not git
On Tue, Jan 25, 2022 at 5:27 PM admin at levyhsu dot com via Gcc-bugs <
gcc-bugs@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103997
>
> --- Comment #14 from Levy Hsu <admin at levyhsu dot com> ---
> Hi Avieira and Richard
>
> I checked the data for the last half month and you are right, that no real
> regression was caused. Thank you all for the detailed explanation.


  reply	other threads:[~2022-01-29 22:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 19:45 [Bug regression/103997] New: " ubizjak at gmail dot com
2022-01-12 19:46 ` [Bug regression/103997] " ubizjak at gmail dot com
2022-01-12 23:13 ` [Bug regression/103997] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-13  3:13 ` crazylht at gmail dot com
2022-01-13  3:27 ` crazylht at gmail dot com
2022-01-13  8:19 ` rguenth at gcc dot gnu.org
2022-01-13  9:17 ` avieira at gcc dot gnu.org
2022-01-13 10:14 ` rguenther at suse dot de
2022-01-13 10:42 ` avieira at gcc dot gnu.org
2022-01-19 14:15 ` cvs-commit at gcc dot gnu.org
2022-01-24  4:00 ` admin at levyhsu dot com
2022-01-24 14:01 ` avieira at gcc dot gnu.org
2022-01-25  6:01 ` admin at levyhsu dot com
2022-01-25 10:01 ` avieira at gcc dot gnu.org
2022-01-25 11:02 ` rguenth at gcc dot gnu.org
2022-01-26  1:27 ` admin at levyhsu dot com
2022-01-29 22:40   ` write2mark1 [this message]
2022-01-29 22:50     ` Andrew Pinski

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='CAE5rLuLkPp6u3FNBdGTJhDFqvyYeF1yVp3xeJ0kRz=xVQgJVvQ@mail.gmail.com' \
    --to=write2mark1@gmail.com \
    --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).