News for hackers. Stuff that matters.
Re:Call for testing: OpenSSH 8.0 by wibble10 on Friday March 29, 2019 @04:45AM (#19520043)
It’s part of OpenBSD who can’t use git for licensing reasons and the switch from cvs->svn isn’t really worth it.

There is a git mirror on github and you can work on that and submit diffs to the mailing list if you’re worried about having to read the cvs manpage ;)

Re:Call for testing: OpenSSH 8.0 by avar on Friday March 29, 2019 @04:57AM (#19520088)
Let's make something clear: They can, and they use other GPL software in the base system.

They just choose not to, for (as I understand it) a combination of reasons. Being averse to relying on new GPL code, being "happy enough" with CVS (also working on OpenCVS), and CVS being a little more than just source control for them due to the likes of CVSync[1].

I have patches in Git. If OpenBSD doesn't want to use it that's fine by me, and I wish them the best of luck. But let's be clear, it's not because we're telling them they can't use it.

1. https://www.openbsd.org/cvsync.html

Re:Call for testing: OpenSSH 8.0 by Crinus on Friday March 29, 2019 @05:33AM (#19520212)
Aren't "patches in Git" just "patches"? Git can give you a patchfile that can be applied with "patch" regardless of VCS.
Re:Call for testing: OpenSSH 8.0 by sneak on Friday March 29, 2019 @06:22AM (#19520386)
from GP: "I have patches in Git. If OpenBSD doesn't want to use it that's fine by me, and I wish them the best of luck. But let's be clear, it's not because we're telling them they can't use it."

I think he means he is a contributor to the source of `git` itself, and thus is justified in saying "we" in terms of not prohibiting OpenBSD's contributors from using the software he helps develop (git).

Re:Call for testing: OpenSSH 8.0 by avar on Friday March 29, 2019 @11:40AM (#19522594)
Correct. Thanks!
Re:Call for testing: OpenSSH 8.0 by simias on Friday March 29, 2019 @05:42AM (#19520254)
>also working on OpenCVS

Are they really though? I can't remember for how long "OpenCVS is to be released soon"[1] but the page itself begins the copyright in 2004.

While I respect other technical decisions taken by the OpenBSD team this one strikes me as pure hubris. Sticking to SVN I could sort-of understand but CVS is just ridiculously frustrating to work with.

[1] https://www.openbsd.org/opencvs/index.html

Re:Call for testing: OpenSSH 8.0 by s_ngularity on Friday March 29, 2019 @06:24AM (#19520399)
Looking at archive.org, the page has had "to be released soon" since at least 2005 [1]. So I think your skepticism is in order.

[1] https://web.archive.org/web/20050130011942/https://www.openb...

Re:Call for testing: OpenSSH 8.0 by jvink on Friday March 29, 2019 @08:21AM (#19520970)
> (also working on OpenCVS)

Not actively. It has been in hybernation for a long time.

Not counting the recently-ish fixes I committed not much is happening with it.

Re:Call for testing: OpenSSH 8.0 by Crontab on Friday March 29, 2019 @05:34AM (#19520215)
Dragonfly has git in base so that, in and of itself, is not the reason why.
Re:Call for testing: OpenSSH 8.0 by wolfy on Friday March 29, 2019 @09:04AM (#19521232)
DragonFly uses git but it's only a package like chromium or xfce.
Re:Call for testing: OpenSSH 8.0 by Crontab on Monday April 01, 2019 @05:03PM (#19548205)
No, it is in the base of the system. I just did an install of the base system and it is there.