From: Tom Tromey <tromey@cygnus.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sourceware.cygnus.com, Mark Mitchell <mark@codesourcery.com>
Subject: Re: libstdc++-v3 module moved into egcs
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200004262200.PAA19847@ferrule.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0004262353040.29901-100000@deneb.dbai.tuwien.ac.at>
>>>>> "Gerald" == Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
>> Speaking as someone whose library might someday be integrated into the
>> gcc tree: I sure see the benefit. I don't want to wade through 1000
>> gcc commits just to see the 3 libgcj commits I'm interested in.
Gerald> I think the better approach here would be to filter your
Gerald> incoming mail using procmail (for example).
I disagree.
Gerald> just imagine every port maintainer of GCC asking for a list of
Gerald> his own!
This is a strawman. It won't happen.
Tom
WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@cygnus.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@sourceware.cygnus.com, Mark Mitchell <mark@codesourcery.com>
Subject: Re: libstdc++-v3 module moved into egcs
Date: Wed, 26 Apr 2000 15:00:00 -0000 [thread overview]
Message-ID: <200004262200.PAA19847@ferrule.cygnus.com> (raw)
Message-ID: <20000426150000.ovivSUvtRpT635s7yu89VnRgK0HhzAWgeF_KlL2edew@z> (raw)
In-Reply-To: <Pine.BSF.4.21.0004262353040.29901-100000@deneb.dbai.tuwien.ac.at>
>>>>> "Gerald" == Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
>> Speaking as someone whose library might someday be integrated into the
>> gcc tree: I sure see the benefit. I don't want to wade through 1000
>> gcc commits just to see the 3 libgcj commits I'm interested in.
Gerald> I think the better approach here would be to filter your
Gerald> incoming mail using procmail (for example).
I disagree.
Gerald> just imagine every port maintainer of GCC asking for a list of
Gerald> his own!
This is a strawman. It won't happen.
Tom
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Benjamin Kosnik
2000-04-21 15:11 ` Benjamin Kosnik
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:08 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-24 10:11 ` Tom Tromey
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:31 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-04-26 14:56 ` Gerald Pfeifer
2000-12-30 6:08 ` Tom Tromey [this message]
2000-04-26 15:00 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda
2000-04-24 10:32 ` Jason Molenda
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:58 ` Jeffrey A Law
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:42 ` Mark Mitchell
2000-12-30 6:08 ` Tom Tromey
2000-04-21 17:13 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda
2000-04-21 17:35 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:47 ` Mark Mitchell
2000-12-30 6:08 ` Jason Molenda
2000-04-21 18:04 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 23:13 ` Mark Mitchell
2000-12-30 6:08 ` Andrew Cagney
2000-04-21 23:29 ` Andrew Cagney
[not found] <39014BB3.B681D244@nabi.net>
2000-12-30 6:08 ` Benjamin Kosnik
2000-04-21 23:56 ` Benjamin Kosnik
2000-12-30 6:08 Benjamin Kosnik
2000-04-24 11:22 ` Benjamin Kosnik
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=200004262200.PAA19847@ferrule.cygnus.com \
--to=tromey@cygnus.com \
--cc=mark@codesourcery.com \
--cc=overseers@sourceware.cygnus.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).