public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Gianni Mariani <marianig@orconet.com>
Cc: Phil Edwards <pedwards@disaster.jaj.com>,
	gcc@gcc.gnu.org, janr@molienergy.bc.ca
Subject: Re: build failure
Date: Wed, 26 Jul 2000 13:17:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.21.0007262214360.9065-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <397E282D.2874A94B@orconet.com>

On Tue, 25 Jul 2000, Gianni Mariani wrote:
> There are patches to apply ?  Am I supposed to  take these patches ?

No, I was talking about patches being submitted to the libstdc++ 3 team.

You don't have to worry about these, the libstdc++ 3 team is taking care
of them and, if suitable, applies them to the CVS repository from where
you will get them automatically next time you download GCC.

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/


  reply	other threads:[~2000-07-26 13:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-25 12:53 Phil Edwards
2000-07-25 16:01 ` Gerald Pfeifer
2000-07-25 16:52   ` Gianni Mariani
2000-07-26 13:17     ` Gerald Pfeifer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-12 12:21 Build failure Jan van Male
2001-06-12 10:30 Jan Kroken
2001-06-12 20:42 ` Alexandre Oliva
2001-06-13  4:56 ` Jan Kroken
2000-07-27 13:01 build failure Phil Edwards
2000-07-27 21:14 ` Marc Espie
2000-07-28 10:15   ` Lee Iverson
2000-07-28 10:32   ` Joern Rennecke
2000-07-27  8:36 Phil Edwards
2000-07-27  9:29 ` Gerald Pfeifer
2000-07-26 10:40 Jan Reimers
2000-07-27 19:10 ` Rich Churcher
2000-07-26 10:33 Phil Edwards
2000-07-27  8:11 ` Gianni Mariani
2000-07-25 17:12 Mike Stump
2000-07-25 16:31 Phil Edwards
2000-07-25 12:22 Jan Reimers

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=Pine.BSF.4.21.0007262214360.9065-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc@gcc.gnu.org \
    --cc=janr@molienergy.bc.ca \
    --cc=marianig@orconet.com \
    --cc=pedwards@disaster.jaj.com \
    /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).