public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94042] [10 Regression] Bootstrap fails on ppc-linux-gnu
Date: Mon, 09 Mar 2020 14:26:29 +0000	[thread overview]
Message-ID: <bug-94042-4-fSTipdYxWc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94042-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #29 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Sorry for all the troubles with my latest patch and thank you for fair
criticism.  I've decided to revert the patch as soon as git starts working. 
I'll work to find a better solution after this.

       reply	other threads:[~2020-03-09 14:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-94042-4@http.gcc.gnu.org/bugzilla/>
2020-03-09 14:26 ` vmakarov at gcc dot gnu.org [this message]
2020-03-09 14:35 ` segher at gcc dot gnu.org
2020-03-09 14:37 ` marxin at gcc dot gnu.org
2020-03-09 14:44 ` segher at gcc dot gnu.org
2020-03-09 14:47 ` segher at gcc dot gnu.org
2020-03-09 14:48 ` segher at gcc dot gnu.org
2020-03-09 14:51 ` marxin at gcc dot gnu.org
2020-03-09 17:52 ` segher at gcc dot gnu.org
2020-03-09 17:53 ` segher at gcc dot gnu.org
2020-03-09 17:54 ` segher at gcc dot gnu.org
2020-03-09 18:09 ` vmakarov at gcc dot gnu.org
2020-03-09 18:15 ` marxin at gcc dot gnu.org
2020-03-09 18:40 ` marxin at gcc dot gnu.org
2020-03-09 21:35 ` segher at gcc dot gnu.org
2020-03-10  8:51 ` marxin at gcc dot gnu.org
2020-03-10  8:57 ` jakub at gcc dot gnu.org
2020-03-10  9:00 ` marxin at gcc dot gnu.org
2020-03-10 15:13 ` segher at gcc dot gnu.org
2020-03-10 15:16 ` marxin at gcc dot gnu.org
2020-03-13 17:54 ` segher at gcc dot gnu.org
2020-03-13 17:55 ` segher at gcc dot gnu.org
2020-03-15 12:02 ` marxin at gcc dot gnu.org
2020-07-13 11:12 ` segher at gcc dot gnu.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-94042-4-fSTipdYxWc@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).