>> What if we switch from CVS to GOT or some other version control system? >> > > Why would there be any issue with the cvsweb links continuing to work with > GOT or another version control system?
you'd need a mapping from each cvs commit to the relevant converted commit. not impossible if a full conversion/cut-across is done, but I think it's of limited use when you can just continue to run cvsweb in parallel. > These URLs are semantic and deterministic. To intentionally break them for > zero real reason, makes little sense. > > The "301 Moved Permanently" redirects are free. they aren't, though it could be mitigated by putting those behind bot checks which are slightly more annoying to the user. (though custom ones don't have to be that annoying ..) > It can be done by a 3-line nginx.conf, after all, which wouldn't be > spawning any new processes to process the requests. it's not running nginx. $ ftp -do/dev/null https://cvsweb.openbsd.org/ host cvsweb.openbsd.org, port https, path , save as /dev/null, auth none. Trying 128.100.17.243... TLS handshake failure: certificate verification failed: unable to get local issuer certificate ermm. $ ftp -S dont -do/dev/null https://cvsweb.openbsd.org/ host cvsweb.openbsd.org, port https, path , save as /dev/null, auth none. Trying 128.100.17.243... Requesting https://cvsweb.openbsd.org/ GET / HTTP/1.1 Connection: close Host: cvsweb.openbsd.org User-Agent: OpenBSD ftp Accept: */* received 'HTTP/1.1 200 OK' received 'Date: Tue, 10 Mar 2026 08:41:11 GMT' received 'Content-Type: text/html; charset=utf-8' received 'Connection: close' received 'Transfer-Encoding: chunked' 2325 bytes received in 0.00 seconds (7.37 MB/s)
