public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@cygnus.com>
To: overseers@sourceware.cygnus.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Mon, 24 Apr 2000 11:22:00 -0000	[thread overview]
Message-ID: <200004241821.LAA01140@haight.constant.com> (raw)
Message-ID: <20000424112200.cBHRq8uHVo8XKiF0Woj6udSg0DAYI7ZwO-XO2Bua0-Q@z> (raw)

The module 'libstdc++-v3' works now, thanks Mark! 

I'm going to go ahead and keep the current repository as is, without
history. I appreciate all the feedback about this, however.


On to other bits:

1) libstdc++-cvs@sourceware.cygnus.com

Yes, I would like a separate list just for libstdc++-v3 check
ins. This is what we currently have, and it is low-volume enough to
actually subscribe to, so yes, I'd like to keep it. Here's how this
might be accomplished:

tom:
"You can do this by editing the gcc commit scripts."

jason:
"If you want a separate commit list, you should probably get Jeff to
create a gcc-libstdc++-cvs@gcc.gnu.org and move over the subscriber
list from the current libstdc++-cvs list."

Hmm. Jeff, is there anyway you can take care of this?


2) libstdc++ web page

Yeah. I'd like to keep separate libstdc++ web pages and mailing lists
for now. I'm trying to make the transition as easy as possible, and if
we want to change this in the future, we can deal with it then.

This is the documentation link in question:

src.egcs/libstdc++-v3/docs/index.html
to
http://sourceware.cygnus.com/libstdc++

jason says:
"You'll need to slightly modify the auto_checkout script in
libstdc++'s CVSROOT to handle its new location, copy it into GCC's
CVSROOT under a different name (e.g. libstdc++-auto-checkout) and add
a line to commitinfo for your new subdir to catch it right.  You can
copy everything from the libstdc++ CVSROOT with minor tweaking for the
new location."

I just modified the old libstdc++/CVSROOT?auto-checkout and checked it in to:

src.egcs/libstdc++-v3/CVSROOT/libstdc++-v3-auto-checkout

I looked at 

src.egcs/CVSROOT/commitinfo

and can't figure out how to make the rest of it happen. Here are the
contents of that file: what needs to change?

DEFAULT         /usr/sourceware/bin/commit_prep -T gcc -r

thanks,
benjamin

             reply	other threads:[~2000-04-24 11:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Benjamin Kosnik [this message]
2000-04-24 11:22 ` Benjamin Kosnik
2000-12-30  6:08 ` bkoz's Fitzcarraldo (was: libstdc++-v3 module moved into egcs) Jason Molenda
2000-04-25 15:13   ` Jason Molenda
2000-12-30  6:08   ` Benjamin Kosnik
2000-04-25 17:10     ` Benjamin Kosnik
2000-12-30  6:08     ` Jason Molenda
2000-04-25 17:51       ` Jason Molenda
2000-12-30  6:08       ` Benjamin Kosnik
2000-04-25 18:30         ` Benjamin Kosnik
2000-12-30  6:08 libstdc++-v3 module moved into egcs 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
2000-04-24 10:11     ` Tom Tromey
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     ` Jeffrey A Law
2000-04-24 10:31       ` Jeffrey A Law
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

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=200004241821.LAA01140@haight.constant.com \
    --to=bkoz@cygnus.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).