From: Tom Tromey <tromey@cygnus.com>
To: Benjamin Kosnik <bkoz@cygnus.com>
Cc: overseers@sourceware.cygnus.com, mark@codesourcery.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Fri, 21 Apr 2000 17:13:00 -0000 [thread overview]
Message-ID: <200004220013.RAA23424@ferrule.cygnus.com> (raw)
Message-ID: <20000421171300.yXY0JhzkP8M8T49HnjTu94faDAH3hRrmVs_1uUqSQRk@z> (raw)
In-Reply-To: <200004212211.PAA01251@haight.constant.com>
Benjamin> 1) Is it possible to remove the old repository? Or to
Benjamin> somehow keep people from being able to check it out?
It is, if that is what you really want.
I thought maybe you would have preferred to copy over the ,v files and
thus keep the revision history.
Benjamin> 2) I need a 'libstdc++-v3' module (or some such name, but
Benjamin> 'libstdc++' is already a module and checks out libstdc++
Benjamin> and libio) so that people can check out just
Benjamin> libstdc++-v3.
You can do this by editing the gcc modules file.
"cvs co CVSROOT"
Benjamin> 3) libstdc++-cvs@sourceware.cygnus.com needs to reflect
Benjamin> checkins in the new repository, not the old one.
You can do this by editing the gcc commit scripts.
Benjamin> 4) The documentation in the CVS repository is the basis for
Benjamin> the libstdc++-v3 on-line documentation. This needs to be
Benjamin> moved over to point to the egcs/libstdc++-v3/docs
Benjamin> directory instead of what's currently in place.
I'm not sure I know what you are talking about here. Which CVS
repository do you mean? What should be moved where?
Tom
next prev parent reply other threads:[~2000-04-21 17:13 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 ` 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
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
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 [this message]
2000-04-21 17:13 ` Tom Tromey
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:42 ` Mark Mitchell
[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=200004220013.RAA23424@ferrule.cygnus.com \
--to=tromey@cygnus.com \
--cc=bkoz@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).