From: Benjamin Kosnik <bkoz@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: hp@bitrange.com, dje@watson.ibm.com, overseers@sources.redhat.com
Subject: Re: htdig and sources.redhat.com loadavg
Date: Mon, 05 Apr 2004 20:48:00 -0000 [thread overview]
Message-ID: <20040405154747.3e47fc75.bkoz@redhat.com> (raw)
In-Reply-To: <20040405194633.GA30430@disaster.jaj.com>
>> (Everyone ok with shutting off gcc htdig permanently?)
>
>Works for me. Anything which can't scan for '++' doesn't really help
>for a C++ library mailing list. Dunno how the rest of gcc feels. :-)
If this was useful for other people, and didn't bring the system to its
knees, then I wouldn't care. As it is, i think htdig is solidly in the
negative side of things.
Personally, I think we should just recommend using google with
site:gcc.gnu.org
-benjamin
next prev parent reply other threads:[~2004-04-05 20:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 18:50 David Edelsohn
2004-04-05 19:36 ` Hans-Peter Nilsson
2004-04-05 19:46 ` Phil Edwards
2004-04-05 19:56 ` Frank Ch. Eigler
2004-04-05 20:03 ` Phil Edwards
2004-04-05 20:36 ` Hans-Peter Nilsson
2004-04-05 21:15 ` Phil Edwards
2004-04-05 21:23 ` Hans-Peter Nilsson
2004-04-05 21:46 ` Phil Edwards
2004-04-05 22:11 ` Hans-Peter Nilsson
2004-04-05 22:26 ` Phil Edwards
2004-04-05 20:48 ` Benjamin Kosnik [this message]
2004-04-05 20:52 ` Ian Lance Taylor
2004-04-05 20:57 ` Zack Weinberg
2004-04-08 21:18 ` Gerald Pfeifer
2004-04-05 21:12 ` Hans-Peter Nilsson
2004-04-05 20:51 ` Christopher Faylor
2004-04-05 21:21 ` Matthew Galgoci
2004-04-05 23:36 ` Zack Weinberg
2004-04-06 0:06 ` Matthew Galgoci
2004-04-06 0:17 ` Matthew Galgoci
2004-04-06 0:29 ` Zack Weinberg
[not found] ` <cgf@alum.bu.edu>
2004-04-05 21:03 ` David Edelsohn
2004-04-05 21:08 ` Ian Lance Taylor
[not found] ` <ian@airs.com>
2004-04-05 21:14 ` David Edelsohn
2004-04-05 22:51 ` Jason Molenda
2004-04-05 23:39 ` GCC snapshot generation (was Re: htdig and sources.redhat.com loadavg) Zack Weinberg
2004-04-06 14:49 ` htdig and sources.redhat.com loadavg David Edelsohn
2004-04-06 16:18 ` Jonathan Larmour
2004-04-06 16:25 ` David Edelsohn
2004-04-06 16:34 ` Ian Lance Taylor
2004-04-06 16:39 ` Phil Edwards
2004-04-07 2:58 ` Christopher Faylor
2004-04-06 16:41 ` Ian Lance Taylor
2004-04-07 2:59 ` Christopher Faylor
2004-04-06 17:40 ` David Edelsohn
2004-04-06 18:00 ` Jonathan Larmour
2004-04-06 19:43 ` Hans-Peter Nilsson
2004-04-06 19:52 ` Frank Ch. Eigler
2004-04-06 23:24 ` Hans-Peter Nilsson
2004-04-06 19:52 ` Ian Lance Taylor
2004-04-08 14:48 ` gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 14:53 ` Frank Ch. Eigler
2004-04-08 15:18 ` Christopher Faylor
2004-05-02 11:32 ` sourceware load problem again? David Edelsohn
2004-04-08 4:04 gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 13:20 ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler
2004-04-08 14:13 ` David Edelsohn
2004-04-08 14:21 ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler
2004-04-08 13:54 ` system rebooted (was Re: gcc.gnu.org CVS meta-data corrupt?) Christopher Faylor
2004-04-29 19:40 sourceware load problem again? David Edelsohn
2004-04-29 19:45 ` Christopher Faylor
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=20040405154747.3e47fc75.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=dje@watson.ibm.com \
--cc=hp@bitrange.com \
--cc=overseers@sources.redhat.com \
--cc=phil@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).