4 ms·

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 wo

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

avar 8y ago
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 https://www.openbsd.org/cvsync.html
- Crinus 8y ago
  Aren't "patches in Git" just "patches"? Git can give you a patchfile that can be applied with "patch" regardless of VCS.
  - sneak 8y ago
    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).
    - avar 8y ago
      Correct. Thanks!
- simias 8y ago
  >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 https://www.openbsd.org/opencvs/index.html
  - s_ngularity 8y ago
    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.openbsd.org/opencvs/index.html https://web.archive.org/web/20050130011942/https://www.openb...
- jvink 8y ago
  > (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.
Crontab 8y ago
Dragonfly has git in base so that, in and of itself, is not the reason why.
- wolfy 8y ago
  DragonFly uses git but it's only a package like chromium or xfce.
  - Crontab 8y ago
    No, it is in the base of the system. I just did an install of the base system and it is there.

avar 8y ago

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 https://www.openbsd.org/cvsync.html

Crinus 8y ago
Aren't "patches in Git" just "patches"? Git can give you a patchfile that can be applied with "patch" regardless of VCS.
- sneak 8y ago
  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).
  - avar 8y ago
    Correct. Thanks!
simias 8y ago
>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 https://www.openbsd.org/opencvs/index.html
- s_ngularity 8y ago
  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.openbsd.org/opencvs/index.html https://web.archive.org/web/20050130011942/https://www.openb...
jvink 8y ago
> (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.

Crontab 8y ago

Dragonfly has git in base so that, in and of itself, is not the reason why.

wolfy 8y ago
DragonFly uses git but it's only a package like chromium or xfce.
- Crontab 8y ago
  No, it is in the base of the system. I just did an install of the base system and it is there.