public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* [overseers] Suggestion to upgrade to CVSweb 3.0
@ 2004-03-12 16:51 Kelley Cook
  2004-03-12 17:02 ` Ian Lance Taylor
  2004-03-12 18:56 ` Joseph S. Myers
  0 siblings, 2 replies; 5+ messages in thread
From: Kelley Cook @ 2004-03-12 16:51 UTC (permalink / raw)
  To: gcc

The GCC website uses cvsweb 1.93 which was a nice stable and old release.

FreeBSD-CVSweb is currently at version 3.0 and offers many compelling 
features including:

automatic tarball/zipball creation
automatic PR xxxxx linking
automatic filename linking
syntax highlighting

The first one alone seems reason enough to upgrade as it would provide 
an alternative for those stuck behind firewalls who are chirping for 
"more snapshots! more snapshots!"

FreeBSD-CVSWeb is available from http://www.freebsd.org/projects/cvsweb.html

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [overseers] Suggestion to upgrade to CVSweb 3.0
  2004-03-12 16:51 [overseers] Suggestion to upgrade to CVSweb 3.0 Kelley Cook
@ 2004-03-12 17:02 ` Ian Lance Taylor
  2004-03-12 18:35   ` Christopher Faylor
  2004-03-12 18:56 ` Joseph S. Myers
  1 sibling, 1 reply; 5+ messages in thread
From: Ian Lance Taylor @ 2004-03-12 17:02 UTC (permalink / raw)
  To: Kelley Cook; +Cc: gcc

Kelley Cook <kcook34@ford.com> writes:

> The GCC website uses cvsweb 1.93 which was a nice stable and old release.
> 
> FreeBSD-CVSweb is currently at version 3.0 and offers many compelling
> features including:
> 
> automatic tarball/zipball creation
> automatic PR xxxxx linking
> automatic filename linking
> syntax highlighting
> 
> The first one alone seems reason enough to upgrade as it would provide
> an alternative for those stuck behind firewalls who are chirping for
> "more snapshots! more snapshots!"

The place to suggest this is overseers@gcc.gnu.org.

My reaction to automatic tarball/zipball creation is "machine
overload! machine overload!"  I think we would definitely want to
disable that feature if we bring in the new cvsweb.

Ian

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [overseers] Suggestion to upgrade to CVSweb 3.0
  2004-03-12 17:02 ` Ian Lance Taylor
@ 2004-03-12 18:35   ` Christopher Faylor
  0 siblings, 0 replies; 5+ messages in thread
From: Christopher Faylor @ 2004-03-12 18:35 UTC (permalink / raw)
  To: Ian Lance Taylor; +Cc: Kelley Cook, gcc

On Fri, Mar 12, 2004 at 12:02:45PM -0500, Ian Lance Taylor wrote:
>Kelley Cook <kcook34@ford.com> writes:
>>The GCC website uses cvsweb 1.93 which was a nice stable and old
>>release.
>>
>>FreeBSD-CVSweb is currently at version 3.0 and offers many compelling
>>features including:
>>
>>automatic tarball/zipball creation automatic PR xxxxx linking automatic
>>filename linking syntax highlighting
>>
>>The first one alone seems reason enough to upgrade as it would provide
>>an alternative for those stuck behind firewalls who are chirping for
>>"more snapshots! more snapshots!"
>
>The place to suggest this is overseers@gcc.gnu.org.
>
>My reaction to automatic tarball/zipball creation is "machine overload!
>machine overload!" I think we would definitely want to disable that
>feature if we bring in the new cvsweb.

Definitely.

cgf

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [overseers] Suggestion to upgrade to CVSweb 3.0
  2004-03-12 16:51 [overseers] Suggestion to upgrade to CVSweb 3.0 Kelley Cook
  2004-03-12 17:02 ` Ian Lance Taylor
@ 2004-03-12 18:56 ` Joseph S. Myers
  2004-03-12 20:05   ` Kelley Cook
  1 sibling, 1 reply; 5+ messages in thread
From: Joseph S. Myers @ 2004-03-12 18:56 UTC (permalink / raw)
  To: Kelley Cook; +Cc: gcc

On Fri, 12 Mar 2004, Kelley Cook wrote:

> FreeBSD-CVSweb is currently at version 3.0 and offers many compelling 
> features including:

Does it fix bugs 2036 (links to diffs for files in Attic don't work; to
test the example URL given you'll need to change "egcs" to "gcc" since
that symlink was removed) or 11335 (incomplete logs shown, possibly
through parsing rlog output and getting confused when something similar
appears in a log message rather than parsing the ,v files properly)?  (I
don't expect anything other than an upgrade to fix these problems; a
previous update did fix bug 638.)

-- 
Joseph S. Myers
jsm@polyomino.org.uk

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [overseers] Suggestion to upgrade to CVSweb 3.0
  2004-03-12 18:56 ` Joseph S. Myers
@ 2004-03-12 20:05   ` Kelley Cook
  0 siblings, 0 replies; 5+ messages in thread
From: Kelley Cook @ 2004-03-12 20:05 UTC (permalink / raw)
  To: Joseph S. Myers, Kelley Cook; +Cc: gcc

"Joseph S. Myers" <jsm@polyomino.org.uk> wrote:
> On Fri, 12 Mar 2004, Kelley Cook wrote:
> 
>> FreeBSD-CVSweb is currently at version 3.0 and offers many
>> compelling features including:
> 
> Does it fix bugs 2036 (links to diffs for files in Attic don't work;
> to test the example URL given you'll need to change "egcs" to "gcc"
> since that symlink was removed) or 11335 (incomplete logs shown, 
> possibly through parsing rlog output and getting confused when
> something similar appears in a log message rather than parsing the 
> ,v files properly)? (I don't expect anything other than an upgrade to
> fix these problems; a previous update did fix bug 638.)

I do not know if it fixes those particular bugs.

I actually started my research because of a bug that appears related to
11335 but specifically related to branches.  I just entered a new PR
web/14561 for it.

Kelley Cook

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-03-12 20:05 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-12 16:51 [overseers] Suggestion to upgrade to CVSweb 3.0 Kelley Cook
2004-03-12 17:02 ` Ian Lance Taylor
2004-03-12 18:35   ` Christopher Faylor
2004-03-12 18:56 ` Joseph S. Myers
2004-03-12 20:05   ` Kelley Cook

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).