public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Benjamin Kosnik <bkoz@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: libstdc++-v3 things that still are not working correctly
Date: Wed, 03 May 2000 22:33:00 -0000	[thread overview]
Message-ID: <27765.957418421@upchuck> (raw)
Message-ID: <20000503223300.DuJyIKjT3Ca1djGKqneEY4mlr7FchPYG2TSir5-IdvQ@z> (raw)
In-Reply-To: <Pine.SOL.3.91.1000503201215.12936B-100000@cse.cygnus.com>

  In message < Pine.SOL.3.91.1000503201215.12936B-100000@cse.cygnus.com >you writ
e:
  > 
  > Please, somebody, help.
  > 
  > 
  > 1) CVS web seems to be pointing at the old repository
That would be a problem with your download.html page.  I tried to fix it,
but the change apparently didn't show up on the web server.



  > 2) html web pages are still not being updated, even with all the latest 
  > greatest helpful hints and everything. 
Well, at least one problem was the loginfo file was wrong.  I still do
not know why it isn't working though.  A "+" in a regexp means one or more
copies of the previously matched pattern.  So "libstdc++-v3" didn't work
like people expected.  Changing it to libstdc..-v3 should help.

I ran into this when fixing #3 below.



  > 3) libstdc++-cvs mapped over to egcs/libstdc++-v3 checkins.
Fixed.
jeff

  parent reply	other threads:[~2000-05-03 22:33 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 cygwin-xfree Chris Faylor
2000-05-03 19:18 ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Jason Molenda
2000-05-03 19:45   ` cygwin-xfree Jason Molenda
2000-12-30  6:08   ` htdig, was cygwin-xfree Frank Ch. Eigler
2000-05-03 20:23     ` Frank Ch. Eigler
2000-12-30  6:08     ` Hans-Peter Nilsson
2000-05-06  2:43       ` Hans-Peter Nilsson
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:53     ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Andrew Cagney
2000-05-03 19:30   ` cygwin-xfree Andrew Cagney
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:34     ` cygwin-xfree Chris Faylor
2000-12-30  6:08   ` cygwin-xfree Jim Kingdon
2000-05-03 19:47     ` cygwin-xfree Jim Kingdon
2000-12-30  6:08 ` cygwin-xfree Jeffrey A Law
2000-05-04  9:07   ` cygwin-xfree Jeffrey A Law
2000-12-30  6:08 ` cygwin-xfree Tom Tromey
2000-05-03 19:59   ` cygwin-xfree Tom Tromey
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 20:07     ` cygwin-xfree Chris Faylor
2000-12-30  6:08     ` cygwin-xfree Per Bothner
2000-05-03 23:21       ` cygwin-xfree Per Bothner
2000-12-30  6:08       ` cygwin-xfree Jim Kingdon
2000-05-04  4:35         ` cygwin-xfree Jim Kingdon
2000-12-30  6:08     ` cygwin-xfree Tom Tromey
2000-05-03 20:09       ` cygwin-xfree Tom Tromey
2000-12-30  6:08       ` cygwin-xfree Chris Faylor
2000-05-03 20:22         ` cygwin-xfree Chris Faylor
2000-12-30  6:08         ` cygwin-xfree Bob Manson
2000-05-03 21:11           ` cygwin-xfree Bob Manson
2000-12-30  6:08           ` cygwin-xfree Jason Molenda
2000-05-04 13:19             ` cygwin-xfree Jason Molenda
2000-12-30  6:08             ` cygwin-xfree Jim Kingdon
2000-05-07  6:32               ` cygwin-xfree Jim Kingdon
2000-12-30  6:08             ` cygwin-xfree Stan Shebs
2000-05-21 22:19               ` cygwin-xfree Stan Shebs
2000-12-30  6:08               ` cygwin-xfree Mark Galassi
2000-05-22  6:15                 ` cygwin-xfree Mark Galassi
2000-12-30  6:08         ` cygwin-xfree Jim Kingdon
2000-05-04  4:52           ` cygwin-xfree Jim Kingdon
2000-12-30  6:08           ` cygwin-xfree Chris Faylor
2000-05-04  7:48             ` cygwin-xfree Chris Faylor
2000-12-30  6:08       ` libstdc++-v3 things that still are not working correctly Benjamin Kosnik
2000-05-03 20:14         ` Benjamin Kosnik
2000-12-30  6:08         ` Jeffrey A Law [this message]
2000-05-03 22:33           ` Jeffrey A Law

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=27765.957418421@upchuck \
    --to=law@cygnus.com \
    --cc=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).