From: Tom Tromey <tromey@cygnus.com>
To: law@cygnus.com
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
overseers@sourceware.cygnus.com, mark@codesourcery.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200004241710.KAA11992@ferrule.cygnus.com> (raw)
In-Reply-To: <6319.956591987@upchuck>
>> 3) libstdc++-cvs@sourceware.cygnus.com needs to reflect checkins in
>> the new repository, not the old one.
Jeff> Actually I think checkin messages should go to gcc-cvs, just
Jeff> like everything else in the gcc repository. I don't see the
Jeff> benefit in separating out the cvs checkin messages for just
Jeff> libstdc++.
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.
Messages can be CC'd to the gcc list if you want to see them that way
for some reason.
Tom
WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@cygnus.com>
To: law@cygnus.com
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
overseers@sourceware.cygnus.com, mark@codesourcery.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Mon, 24 Apr 2000 10:11:00 -0000 [thread overview]
Message-ID: <200004241710.KAA11992@ferrule.cygnus.com> (raw)
Message-ID: <20000424101100.Fd_w9asqbsRueZk7Izkbe9maRZC8LmEWHP_fUr6Sjdk@z> (raw)
In-Reply-To: <6319.956591987@upchuck>
>> 3) libstdc++-cvs@sourceware.cygnus.com needs to reflect checkins in
>> the new repository, not the old one.
Jeff> Actually I think checkin messages should go to gcc-cvs, just
Jeff> like everything else in the gcc repository. I don't see the
Jeff> benefit in separating out the cvs checkin messages for just
Jeff> libstdc++.
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.
Messages can be CC'd to the gcc list if you want to see them that way
for some reason.
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 ` Mark Mitchell
2000-04-21 17:42 ` Mark Mitchell
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:08 ` Jeffrey A Law
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 ` Tom Tromey [this message]
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
2000-04-26 15:00 ` Tom Tromey
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
-- strict thread matches above, loose matches on Subject: below --
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=200004241710.KAA11992@ferrule.cygnus.com \
--to=tromey@cygnus.com \
--cc=bkoz@cygnus.com \
--cc=law@cygnus.com \
--cc=mark@codesourcery.com \
--cc=overseers@sourceware.cygnus.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).