Comment by dsr_
10 years ago
For 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.
> As a result, Linus wrote git.
And mpm wrote hg, never forget:
http://lkml.iu.edu/hypermail/linux/kernel/0504.2/0670.html
http://lwn.net/Articles/151624/
It's astonishing to me that Git has won out given how much easier it's been for me to explain Hg to other people than to explain Git. To this day, in our SVN workflow at my company, nontechnical people who have merely seen a Hg diagram on a whiteboard by my desk immediately grasped the idea and the lingo, and ask me questions like "hey, can you branch the code to commit those changes and push them to the testing server? This thing's really cool and we don't mind playing with the alpha version, but we might scrap it all later."
Maybe I'm a too long time user of git, but I really fail to see why git as of the last 5 years is any harder to explain than hg. Personally I think the branching in hg is pretty much broken; alone the fact that it's pretty much impossible to get rid of branches is horrible.
11 replies →
This applied to me as well. I like the metaphor someone wrote that Git is the assembly language of DCVS.
1 reply →
"hey, can you branch the code to commit those changes and push them to the testing server? This thing's really cool and we don't mind playing with the alpha version, but we might scrap it all later."
Are they talking about hg or git here. Because that flow in git is:
The only thing that git adds to that workflow is that creating a new branch doesn't immediately move you onto it (also that most would use checkout -b to do both). And it's not immediately obvious that a non-technical user would need to know about that in order to get the above point across.
14 replies →
git is the primary example of how bad Linus Torvalds is at writing UI code.... ;o)
From what I read, he connected to a bit keeper repository via telnet on port 5000, executed the help command and then used that information to write an incomplete client. That does not sound like reverse engineering to me.
It is reverse engineering. It's just easy reverse engineering.
As I remember it, it was a bit of a douche move by Tridgell, driven by a Stallman-like free software ideology.
It wasn't. He gave conclusive reply which established that it's ethical (just telneting and help). Unless you believe samba and everything else is unethical and you club every reverse engineering under one umbrella, your comment is wrong. http://www.theregister.co.uk/2005/04/14/torvalds_attacks_tri...
I don't think it's fair to call people douches because they are committed to their moral principals. Especially so here, where the benefit to humanity over the alternative is so clearly obvious.
It is when they attempt to force their moral code on others.
Is the benefit clearly obvious? If you actually adhere 100% to Stallman's code I'm not so sure.
1 reply →
> a Stallman-like free software ideology
You say that like it's a bad thing.
As I remember it, he did
telnet bk-server 5000
and typed "help".
https://lwn.net/Articles/132938/
That's the "how" not the "why".
So having a genuine need to be able to actually use tools that you wrote rather than something a company 'licenses' to you so that can modify, and share these tools is being a douche? Odd that you would think that companies that treat their users like untrustworthy hackers are not douches but those users are!
Here's an article about that: http://www.theregister.co.uk/2005/04/14/torvalds_attacks_tri...