|
|
|
|
|
|
ot Sava CHankov(21-04-2005)
Sled kato BitMover Inc. (proizvoditeliat na BitKeeper - sistemata za kontrol na versii, izpolzvana za razrabotka na iadroto Linux) prekrati bezplatniia litsenz, Linus Torvalds zaedno s drugi razrabotchitsi na iadroto se e zahvanal da razraboti sobstven instrument za tazi tsel.
Korporatsiiata BitMover Inc. e prekratila bezplatniia litsenz zaradi reversivnoto inzhinerstvo na neiniia produkt ot Andryu Tridzhul (koito v minaloto e postignal dosta uspehi v tazi oblast). Linus e vidimo nedovolen ot deistviiata na Tridzhul, narichaiki proekta mu "losh".
Razrabotkata na sobstvena sistema za kontrol na versiite se nalaga zashtoto sushtestvuvashtite (vklyuchitelno populiarnata CVS) se spraviat dosta zle s proekt ot takava velichina. "Desetki sekundi za prilaganeto na krupka prosto ne e priemlivo vreme", kazva Linus.
Po dumite na Torvalds, novata sistema, narechena ne bez chuvstvo za humor git (angl. - mizernik), e " glupav(no mnogo burz) upravitel na sudurzhanieto na direktorii. Ne mozhe da pravi mnogo, no tova, koeto _pravi_, e da upravliava sudurzhanieto na direktoriite efikasno". Novata versiia na iadroto, 2.6.12-rc3, e napravena s neina pomosht. Dosta novini za napreduka i izlizat na kerneltrap.org
<< Utre zapochva WebTech 2005 - Sofiia | Indiia spira softuernite patenti. >>
|
|
|
|
|
Komentar ot: Georgi CHorbadzhiiski georgi__at__unixsol__dot__org |
Data: 21-04-2005 |
[ Drugi komentari] |
Spored Linus e baven. Mislia che choveka znae nai-dobre, vse pak toi shte raboti iako s utilkata, taka che predi da sedne da si pishe e probval, testval i e vidial che ne stava. Nito arch, nito monotone, za cvs da ne govoria, a puk razrabotchitsite na svn spetsialno otvoreno pismo napisaha kum yuzurite da ne tormoziat Linus s predlozheniia da polzva svn, shtoto ne mu vurshi rabota :)
btw: vizhte http://kerneltrap.com/ tam ima niakolko statii za git, prochetete komentarite i shte razberete zashto drugite ne stavat.
TSitiram kakvo beshe napisano v edin ot komentarite (v nego dobre se obiasniava kakuv e problema)
http://kerneltrap.org/node/5014
"Most SCMs are designed to work on the "I'm the boss and I pay your wages, you'll do what I tell you" basis. For the BSDs that works because you have one guy controlling everything and a *s*m*a*l*l* team of developers. So you have ONE master setup, and everybody works in their own little patch of it - management ensuring that you don't get two people working on the same stuff at the same time.
That last sentence is the BIG PROBLEM behind most SCMs. They cannot cope with "several workers, one bit of code". Two workers trying to check out the same bit of code? Most SCMs have conniptions and then fall over in a heap. Then try and use that to manage Linux, where you get hundreds of developers all falling over the same *few* *lines* *of* *code* to fix a bug or whatever, and pretty much any semi-commercial SCM is dead in the water even before it's gone down the slipway!
The reason BK was so good for Linus is that (a) it allowed every developer to have their *own* *master* version, and (b) it allowed every developer to say "I want *these* changes, but *not* *those*, from *that* master tree". So, for example, Andrew Morton maintains the mm testing tree with maybe 30 different enhancements over Linus' main tree. And when Linus decided that feature X was mature enough, he did a "bk get" on *just* *that* *one* *feature*.
CVS, being file based, would have been a pain. And, to make it worse, if several other features had been added to the files Linus wanted, he would have got those features as well.
Basically, BK (and now git) are different from other SCMs because they have distributed masters, not just one HEAD, and they allow selective merging of feature sets between trees, not simply checking in and out individual files."
....i ne na posledno miasto sa BURZI.
Oshte edin tsitat ot tazi stranitsa:
All indications are that within a few weeks, git will become a better SCM for the kernel project than any other free SCM is today. Partly that's because it is focused very narrowly (for now) on features and constraints of the kernel. But partly it's because Linus has taken a fresh look at SCM, has come up with some innovative ideas, and is leveraging highly incremental development (and a handful of eager volunteers) to make rapid progress.
git is self-hosting (and has been from very early on), and is already being used for actual kernel work. That's pretty impressive.
Redaktiran na: 21-04-2005@21:10
|
<< Kum: Kum: CVS -> git!!! | Kum: CVS -> git!!! >> |
|
|
|
|
|
|
|
|