public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.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 18:07:00 -0000 [thread overview]
Message-ID: <20021114172604.6759.qmail@sources.redhat.com> (raw)
The following reply was made to PR web/638; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, 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: 14 Nov 2002 10:18:10 -0700
>>>>> "Jason" == Jason Molenda <jason-gcclist@molenda.com> writes:
Jason> The best one could hope for is to look at viewcvs and see if
Jason> they've solved this problem.
I've looked into this problem before.
Fixing it in cvsweb looked like a pain. As I recall I couldn't find a
way to get rcsdiff to generate the diff we need.
I also talked to the viewcvs maintainers about this. They seemed
receptive to the idea of adding the needed feature, but I don't know
whether it ever happened. I suspect not, since I remember downloading
viewcvs last year and deciding not to install it. I'm sure I would
have investigated this feature then.
Tom
next reply other threads:[~2002-11-14 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 18:07 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 15:00 jsm28
2002-11-20 9:26 Jason Molenda
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=20021114172604.6759.qmail@sources.redhat.com \
--to=tromey@redhat.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).