>>In contrast, with git, I'm totally uninterested in anything that doesn't >>make my kernel work go faster or more smoothly, and does so _today_. Which >>makes me a cantancerous old bastard, and bit the heads off anybody who >>isn't focused on that one thing. Focus is the totally operative word here! If you really want to feel good about the world, re-read the initial set of git postings that Linus made on April 7th: http://kerneltrap.org/node/4982 Contrast the picture today with the fact that three weeks ago: April 7: 1) the kernel workflow was at a standstill 2) git was just a totally unproven concept in Linus' head, that could have ended up as a band-aid while a REAL SCM (...sound of choking from the wings...) was chosen 3) the performance issues in dealing with both the size of the kernel project, and the velocity of the changes were completely up in the air Today: 1) the kernel workflow has restarted, and has already made its first milestone 2) git is solid in architecture, is maintained and updated by a proven set of developers, and has been demonstrated to have all the performance necessary going forward 3) the primary traffic on the mailing list is related to tactical issues - not architecture, or strategy, or big-ticket item stuff - with the occasional flame about "renames" ;-) Are there any large strategic issues left to be resolved for git?, or is it just a matter of getting all the kernel developers over the learning curve, and iterating the details of the workflow to make everyone maximally productive? How long do you think it will take for the kernel workflow to get back to its height during the BK days? The achievement of going from a complete standstill, to full velocity kernel workflow production in a couple of months has got to be something everyone involved should be intensely proud of. Thanks, Linus, for being such a "cantancerous old bastard". I don't think it could have happened if you were anything but.... Barry Silverman - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Apr 29 01:05:58 2005
This archive was generated by hypermail 2.1.8 : 2005-04-29 01:05:59 EST