Re: cvsweb news

On 09/03/2026 19:24, Nick Holland wrote:
> On 3/8/26 4:38 PM, Constantine A. Murenin wrote:
>> These are all still broken:
>>
>> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/
>> <http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/>
>> http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/
>> <http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/>
>> http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/
>> <http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/>
>>
>> Nick, can we have that fixed, please?
>>
>> These have been spattered throughout the mailing list archives,
>> research papers etc etc, and cannot be fixed upstream.
>
> What if we switch from CVS to GOT or some other version control system?
> After 43 years working in IT, one thing I know: change happens. 

OMG don't let that Andy Wallis character hear this

> I'm not terribly interested in backwards compatibility.  Keep in mind, the
> alternative to this wonderful application Ken has written was likely to
> become complete unavailability of the info via the web.  Ultimately,
> though,
> Ken wrote the code, he'll be the one to make the call on this, but he and I
> are currently on the same page, it seems.  The change in URLs is

this. go Git, and Ken instead of writing incomplete web guis can port
any tools that CVS used and that would be needed for git.

why git and not got? more popular, and hence more automated. got is a
niche project. git isn't. a lot of cool shit is already available on the
market for it, e.g. cgit which works very very well.