Linux is now hosted on GitHub
github.com
github.com
linux-2.6 $ git pull git://github.com/torvalds/linux.git
linux-2.6 $ git fetch --tags git://github.com/torvalds/linux.git
linux-2.6 $ gpg --keyserver pgp.mit.edu --recv-keys 76E21CBB
linux-2.6 $ git verify-tag v3.1-rc5
gpg: Signature made Sun 04 Sep 2011 06:45:37 PM EDT using DSA key ID 76E21CBB gpg: Good signature from "Linus Torvalds (tag signing key) <torvalds@osdl.org>"
If you don't trust the key of anyone that has verified his key (which is true in my case), attend more signings.
Look at his public activity [1]: comments, pull requests, issues… he is using GitHub, for real.
Which, this makes me wonder what will happen when someone forks "linux" and sends Linus a pull request. ;-)
BitKeeper actually prohibits their customers from contributing to competing projects? They forced some guy to stop working on Mercurial in his free time because he used BitKeeper at work and they were afraid that he "might be moving BitKeeper technology into Mercurial." That's an impressive level of evil.
(See http://en.wikipedia.org/wiki/BitKeeper http://article.gmane.org/gmane.comp.version-control.mercuria... )
BitKeeper actually prohibits their customers from contributing to competing projects?
Using the product to reverse-engineer a protocol to develop a free client is not 'contributing to a competing product'. Which is against their license (though that may be void because the law grants you reverse-engineering rights, no matter what a license says. Otherwise nothing could ever be reverse-engineered at all). they were afraid that he "might be moving BitKeeper technology into Mercurial."
That's entirely reasonable. If you have deep knowledge of how proprietary system A works and are hacking on free system B that purports to do the same thing, there is every chance you inadvertently include proprietary knowledge into your code for the free product. It's very hard to avoid using the knowledge you have.a) I'm not talking about the reverse-engineering thing. Them wanting to shut that down is somewhat reasonable.
b) I don't think this guy had "deep knowledge of how [BitKeeper] works." He just used BitKeeper at his job. Most people who use git don't have a deep understanding of how it works. They just know how to make it manage their code. It feels pretty evil to me to provide a general development tool and put limitations on what any developer who uses it may do. What if Microsoft said in their license, "If you are a Windows user, you may not contribute to any other operating system."? We'd complain about how evil and anticompetitive Microsoft is.
Don't expect people to be bound by forced promises.
If I was in a different societal context where I could say 'No', and you know, shoot someone if they got pushy about it, then I'd be truer to my word. But given that I can't there's no choice but to lie - I'm certainly not going to stop learning just because someone told me to to preserve his market share.
Also, the same thing applies to DRM removal, etc. Once I buy a product it's mine - be thankful I didn't just warez it in the first place.
Also http://www.theregister.co.uk/2005/04/14/torvalds_attacks_tri...
git was developed because developers of BT stopped licensing it to Linux kernel developers with special terms, and Linus needed something as powerful.
I see it as Tridge simply accelerating the natural course of events, not actually causing them.
He telneted the bk server and typed 'help'. It gave him a list of commands, and what they did.
LWN article on it: http://lwn.net/Articles/132938/
I know nothing important was compromised, but nobody likes to deal with being hacked. It's like being the victim in a car accident- insurance makes you whole, but the whole experience sucks all the same.
If it's on the net it's at risk.
Mainly I would say that it works great for projects with relatively few contributors (like most Ruby gems), but seems to fall apart on very large projects (like Rails, who uses Lighthouse for issue tracking). Everything else about Github is amazing, though.
dhh doesn't sound like he was ever a fan of Lighthouse: https://twitter.com/#!/dhh/status/63366853636009985
Once again: trac is REALLY GOOD and no other project can compete for clarity and all other words form that UX crap. ^_^
Also, what does Webkit have to do with Trac?
Emacs. Tag search. Problem: solved.
My life has been infinitely enriched by the countless hours I've spent, many a dark night, in /usr/src/linux[1], with "Midnight Commander".
[1] A symlink, always a symlink.
As for descriptive names, I agree.
Kernel issues are tracked through distributions' bug trackers, bugzilla.kernel.org, and ultimately the mailing list.
[1] http://thread.gmane.org/gmane.linux.kernel/1187888/focus=118...
This page helped me a lot: https://help.ubuntu.com/community/Kernel/Compile#AltBuildMet...
I suppose it comes as no surprise that Linux makes extensive use of Git's features.
That said, Linux is a huge project with tons of contributors.
RoR: Large number of contributors with relatively small patches, few full time contributors who are paid just to work on RoR.
Linux: Possibly smaller number of overall contributors but supplying more patches each, and more patches in total. More contributors who are paid to work on the kernel on a full or part time basis.
Linux is, perhaps, the most rapidly changing piece of software in existence
linux-3.1-rc3$ ls -R -l |wc -l
46855
linux-3.1-rc3$ du -h -s
500M
rails$ ls -R -l |wc -l
4141
rails$ du -h -s
59M .