public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Molenda <jason-gcclist@molenda.com>
To: overseers@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: web/638: Broken gcc-cvs links
Date: Wed, 20 Nov 2002 09:26:00 -0000 [thread overview]
Message-ID: <20021114084609.20541.qmail@sources.redhat.com> (raw)
The following reply was made to PR web/638; it has been noted by GNATS.
From: Jason Molenda <jason-gcclist@molenda.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: neroden@gcc.gnu.org, gcc-bugs@gcc.gnu.org, overseers@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Subject: Re: web/638: Broken gcc-cvs links
Date: Thu, 14 Nov 2002 00:37:05 -0800
On Thu, Nov 14, 2002 at 08:26:53AM +0000, Joseph S. Myers wrote:
> It is not working. The link in the PR does not work, and such links are
> still being generated (for example,
> <http://gcc.gnu.org/ml/gcc-cvs/2002-11/msg00345.html> contains such a
> link).
Not to be a Negative Nelly, but I don't expect this to get fixed any
time soon. No one among the sources/gcc.gnu.org maintainers have
jumped at it; the cvsweb maintainers have wandered off to other
things, and cvs in general is an unloved, can't-get-replaced-quick-enough
child of the free software world.
The best one could hope for is to look at viewcvs and see if they've
solved this problem. But if I'm not mistaken, even they have their
eyes cast towards svn these days.
J
next reply other threads:[~2002-11-14 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 9:26 Jason Molenda [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 15:00 jsm28
2002-11-20 18:07 Tom Tromey
2002-11-20 9:23 Joseph S. Myers
2002-11-20 7:19 neroden
2001-08-10 0:25 gerald
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=20021114084609.20541.qmail@sources.redhat.com \
--to=jason-gcclist@molenda.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
/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).