public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/63958] [5 Regression] bootstrap failure in the sanitizer libs on sparc-linux-gnu
Date: Wed, 19 Nov 2014 21:20:00 -0000	[thread overview]
Message-ID: <bug-63958-4-NQcKQgIcW5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63958-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
I am very sorry that you are so upset, but the workflow will not change. 
All changes to sanitizer files (except for GCC-specific tests and make files)
have to go to upstream first. 
If any change goes directly to GCC it will get overwritten by a following merge
from upstream. 
(merge is the wrong name for process actually. The right name would be "copy").


  parent reply	other threads:[~2014-11-19 21:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 11:51 [Bug sanitizer/63958] New: " doko at gcc dot gnu.org
2014-11-19 12:33 ` [Bug sanitizer/63958] " rguenth at gcc dot gnu.org
2014-11-19 19:26 ` kcc at gcc dot gnu.org
2014-11-19 21:20 ` kcc at gcc dot gnu.org [this message]
2014-11-19 22:13 ` davem at gcc dot gnu.org
2014-11-19 22:25 ` kcc at gcc dot gnu.org
2014-12-10 15:30 ` rguenth at gcc dot gnu.org
2015-02-24 11:22 ` jakub at gcc dot gnu.org
2015-02-26  9:41 ` doko at gcc dot gnu.org
2015-03-09 18:26 ` jakub at gcc dot gnu.org
2015-03-09 19:05 ` jakub at gcc dot gnu.org
2015-03-09 19:26 ` jakub at gcc dot gnu.org
2015-10-21  7:45 ` chefmax 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-63958-4-NQcKQgIcW5@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).