3 ms·
It's easier to write git if you have a CVS repo to store your work in Not to diminish your point or anything, but regarding Git, I'll just quote Linus Tol
by bad_user 15y ago
It's easier to write git if you have a CVS repo
to store your work in
Not to diminish your point or anything, but regarding Git, I'll just quote Linus Tolvards:
For the first 10 years of kernel maintenance, we
literally used tarballs and patches, which is a much
superior source control management system than CVS is
Basically Git started as a bunch of scripts written by Linux for dealing with "tarballs and patches" and nobody starts something like this unless there's lots of hatred involved. What you get if you're a CVS user and want something better is SVN. You get Git when you consider CVS such an abomination that you'd rather do without any existing VCS altogether.
And I really think the world needs more people like Linus, as some wheels are worth reinventing.
The real fundamentals of computing happened a long
time ago.
In the words of Alan Kay: The computer revolution hasn't happened yet ... http://video.google.com/videoplay?docid=-2950949730059754521 http://video.google.com/videoplay?docid=-2950949730059754521 (listen to this talk because it's great).
- scott_s 15y agoI think it's worth noting that git did not replace tarballs and patches. Git replaced Bitkeeper. Bitkeeper, as far as I know, replaced tarballs and patches. And as far as I know, git did not start as a bunch of scripts for dealing with tarballs and patches. The design was inspired by his knowledge of and experience with Bitkeeper.
- bad_user 15y agoThe workflow was indeed inspired by Bitkeeper, nothing is truly revolutionary, but Bitkeeper itself was not the status quo in a world dominated by CVS, SVN and Perforce. On "tarballs and patches", I was referring to this famous quote from http://marc.info/?l=linux-kernel&m=111288700902396 http://marc.info/?l=linux-kernel&m=111288700902396 ... So I'm writing some scripts to try to track things a whole lot faster. Initial indications are that I should be able to do it almost as quickly as I can just apply the patch, but quite frankly, I'm at most half done, and if I hit a snag maybe that's not true at all. Anyway, the reason I can do it quickly is that my scripts will _not_ be an SCM, they'll be a very specific "log Linus' state" kind of thing. That will make the linear patch merge a lot more time-efficient, and thus possible.
- scott_s 15y agoBitkeeper was not the status quo, but I don't think that's important in the overall point. The original point was that git was inspired by previous software. The original software pointed at, cvs, was wrong, but I don't think the original point changes when we put the correct software, Bitkeeper, in its place in the sentence.
- thebigshane 15y agoI think Alan Kay would disagree with you: http://stackoverflow.com/questions/432922/significant-new-inventions-in-computing-since-1980 http://stackoverflow.com/questions/432922/significant-new-in... The basic idea here is not to bash the current state of things but to try to understand something about the progress of coming up with fundamental new ideas and principles. I claim that we need really new ideas in most areas of computing, and I would like to know of any important and powerful ones that have been done recently. If we can't really find them, then we should ask "Why?" and "What should we be doing?" Which sounds to me like "The real fundamentals of computing happened a long time ago." Perhaps there will be a more significant revolution in our future but that doesn't contradict the above statement.
- bad_user 15y agoOMG, Alan Kay is on Stack Overflow? That's freaking awesome :)