Earlier quoted context omitted.
You wouldn't, unless you have very specific niche needs. They're pretty upfront about it: >Why use BitKeeper when there are lots of great alternatives? >For many projects, the answer is: you shouldn’t. https://www.bitkeeper.org/why.html
Probably the single biggest reason, aside from it's easier to use than git's CLI, is that it has sub-modules that work exactly like files do in a repository. No extra options, just clone/pull/push/commit/etc. Full on distributed workflow. BitKeeper itself is a collection of repositories. Download an install image, install, and clone it: $ bk clone http://bkbits.net/u/bk/bugfix $ cd bugfix $ bk here PRODUCT default $…
Show HN: BitKeeper – Enterprise-ready version control, now open-source
21–30 of 309 posts
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#22For people who don't know the history -- McVoy offered free bitkeeper licenses to various open source projects, and the Linux kernel switched to it. After Andrew Tridgell (SAMBA, among other projects) reverse-engineered the bitkeeper protocol [1] in order to create his own client, the license was rescinded for everyone. As a result, Linus wrote git. [1] https://lwn.net/Articles/132938/
As I remember it, it was a bit of a douche move by Tridgell, driven by a Stallman-like free software ideology.
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#23For people who don't know the history -- McVoy offered free bitkeeper licenses to various open source projects, and the Linux kernel switched to it. After Andrew Tridgell (SAMBA, among other projects) reverse-engineered the bitkeeper protocol [1] in order to create his own client, the license was rescinded for everyone. As a result, Linus wrote git. [1] https://lwn.net/Articles/132938/
As I remember it, it was a bit of a douche move by Tridgell, driven by a Stallman-like free software ideology.
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#24For people who don't know the history -- McVoy offered free bitkeeper licenses to various open source projects, and the Linux kernel switched to it. After Andrew Tridgell (SAMBA, among other projects) reverse-engineered the bitkeeper protocol [1] in order to create his own client, the license was rescinded for everyone. As a result, Linus wrote git. [1] https://lwn.net/Articles/132938/
As I remember it, it was a bit of a douche move by Tridgell, driven by a Stallman-like free software ideology.
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#25Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#26For people who don't know the history -- McVoy offered free bitkeeper licenses to various open source projects, and the Linux kernel switched to it. After Andrew Tridgell (SAMBA, among other projects) reverse-engineered the bitkeeper protocol [1] in order to create his own client, the license was rescinded for everyone. As a result, Linus wrote git. [1] https://lwn.net/Articles/132938/
And mpm wrote hg, never forget:
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#27For people who don't know the history -- McVoy offered free bitkeeper licenses to various open source projects, and the Linux kernel switched to it. After Andrew Tridgell (SAMBA, among other projects) reverse-engineered the bitkeeper protocol [1] in order to create his own client, the license was rescinded for everyone. As a result, Linus wrote git. [1] https://lwn.net/Articles/132938/
As I remember it, it was a bit of a douche move by Tridgell, driven by a Stallman-like free software ideology.
You say that like it's a bad thing.
Re: Show HN: BitKeeper – Enterprise-ready version control, now open-source
#28Um, the "because" part is not quite right.