From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Andreas Jaeger <aj@suse.de>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: Java/parellel build(?) related bootstrap failure
Date: Mon, 31 Mar 2003 07:47:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.53.0303310006410.36800@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <u8llywq5eq.fsf@gromit.moeb>
On Sun, 30 Mar 2003, Andreas Jaeger wrote:
> Gerald, perhaps you also miss the directory? Run cvs update -d to get
> new directories,
Argl, it seems that one tester was indeed lacking -d to avoid getting
gcc/ada. Sorry folks!
Now, isn't there _some_ way to use cvs update -d and still being able to
avoid certain "new" directories like /gcc/ada?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-03-30 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 15:44 Gerald Pfeifer
2003-03-29 17:16 ` Andreas Jaeger
2003-03-30 22:02 ` Andreas Jaeger
2003-03-31 7:47 ` Gerald Pfeifer [this message]
2003-03-31 8:38 ` Andrew Haley
2003-04-01 23:38 ` Gerald Pfeifer
2003-04-01 23:44 ` Gerald Pfeifer
2003-04-02 0:13 ` Daniel Jacobowitz
2003-04-02 12:06 ` Andrew Haley
2003-03-30 7:36 ` Tom Tromey
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.53.0303310006410.36800@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=java@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).