public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Andreas Tobler <toa@pop.agri.ch>
Cc: gcc@gcc.gnu.org, mark@codesourcery.com
Subject: Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
Date: Sat, 05 Oct 2002 04:00:00 -0000	[thread overview]
Message-ID: <u8it0hw6qd.fsf@gromit.moeb> (raw)
In-Reply-To: <3D9EB5F3.2050607@pop.agri.ch> (Andreas Tobler's message of "Sat, 05 Oct 2002 11:50:43 +0200")

Andreas Tobler <toa@pop.agri.ch> writes:

> H. J. Lu wrote:
>
>>>>/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
>>>>   type named `allocator_type' in `struct
>>>> __gnu_cxx::_Rope_rep_base<char,   std::allocator<char> >'
> []
>> Mark, Andreas has identified your patch breaks both mainline and 3.2:
>> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
>> Shouldn't we revert it at least on the 3.2 branch?
>
> What is about the trunk? Do we wait?

According to our development rules, we wait 48 hours and then even
need some approval of two other developers:

    If a patch is committed which introduces a regression [1], on any
    target which the Steering Committee considers to be important [2],
    and the problem is reported to the original poster, and 48 hours
    pass without either the original poster or any other party
    indicating that a fix will be forthcoming in the very near future,
    and two people with write privileges to the affected area of the
    compiler determine that the best course of action is to revert the
    patch, then they may revert the patch.

But I do expect that Mark will be back from vacation on the 8th and
fix it immediatly.  The question is whether we wait so long or not.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-10-05  9:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04  1:59 H. J. Lu
2002-10-04  6:03 ` kwall
2002-10-04  9:51 ` Janis Johnson
2002-10-04  9:56   ` H. J. Lu
2002-10-04 10:05     ` H. J. Lu
2002-10-04 11:43       ` PATCH: Revert part of c++ change (Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?) H. J. Lu
2002-10-05  3:33     ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
2002-10-05  4:00       ` Andreas Jaeger [this message]
2002-10-05 11:21         ` Fergus Henderson
2002-10-05 13:56           ` Andreas Jaeger
2002-10-06  0:12             ` Fergus Henderson
2002-10-08  3:02           ` Mark Mitchell

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=u8it0hw6qd.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=toa@pop.agri.ch \
    /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).