From: Jason Molenda <jason-swarelist@molenda.com>
To: Tom Tromey <tromey@cygnus.com>
Cc: Overseers List <overseers@sourceware.cygnus.com>
Subject: Re: FYI: ViewCVS
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000819121953.A22015@shell17.ba.best.com> (raw)
In-Reply-To: <87bsyp6ps7.fsf@creche.i-did-not-set--mail-host-address--so-shoot-me>
On Sat, Aug 19, 2000 at 12:59:04PM -0600, Tom Tromey wrote:
> ViewCVS is a reimplementation of cvsweb in Python:
Yah, I'd seen that before - IIRC they were about on par with cvsweb's
level of features a while ago.
You can always install both of them.
BTW I believe there was a bugtraq sort of report about some possible
exploits in the older cvsweb version we're running on sourceware. It'd
probably be good to grab the latest and install it some time - I'm using
it at Yahoo with no problems. (I keep meaning to do it myself but have
yet to actually get around to it)
> I'm going to ask him about the `NONE' problem -- if ViewCVS
> solves that then it might be reason enough to change.
I kind of doubt it, unless it's parsing the RCS files on its own.
cvsweb uses rdiff to do the diff-without-a-checkout, and rdiff is
implemented within cvs and is missing many of the features of the
normal diff, making any kind of reasonable workaround for the NONE
diffs impossible. (at least that's the conclusion I came to when
I looked at fixing this a couple of months ago)
Jason
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Tom Tromey <tromey@cygnus.com>
Cc: Overseers List <overseers@sourceware.cygnus.com>
Subject: Re: FYI: ViewCVS
Date: Sat, 19 Aug 2000 12:20:00 -0000 [thread overview]
Message-ID: <20000819121953.A22015@shell17.ba.best.com> (raw)
Message-ID: <20000819122000.Yt3MBej1-mB_ijn97S8cXhYjXv03SHyEGCzLhJquTeU@z> (raw)
In-Reply-To: <87bsyp6ps7.fsf@creche.i-did-not-set--mail-host-address--so-shoot-me>
On Sat, Aug 19, 2000 at 12:59:04PM -0600, Tom Tromey wrote:
> ViewCVS is a reimplementation of cvsweb in Python:
Yah, I'd seen that before - IIRC they were about on par with cvsweb's
level of features a while ago.
You can always install both of them.
BTW I believe there was a bugtraq sort of report about some possible
exploits in the older cvsweb version we're running on sourceware. It'd
probably be good to grab the latest and install it some time - I'm using
it at Yahoo with no problems. (I keep meaning to do it myself but have
yet to actually get around to it)
> I'm going to ask him about the `NONE' problem -- if ViewCVS
> solves that then it might be reason enough to change.
I kind of doubt it, unless it's parsing the RCS files on its own.
cvsweb uses rdiff to do the diff-without-a-checkout, and rdiff is
implemented within cvs and is missing many of the features of the
normal diff, making any kind of reasonable workaround for the NONE
diffs impossible. (at least that's the conclusion I came to when
I looked at fixing this a couple of months ago)
Jason
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Tom Tromey
2000-08-19 11:52 ` Tom Tromey
2000-12-30 6:08 ` Jason Molenda [this message]
2000-08-19 12:20 ` Jason Molenda
2000-12-30 6:08 ` Tom Tromey
2000-08-19 12:35 ` Tom Tromey
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=20000819121953.A22015@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sourceware.cygnus.com \
--cc=tromey@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).