3 ms·
The 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
by bad_user 15y ago
The 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.