Mercurial > hgbook
changeset 387:1604f2b2054b
more intro.tex
| author | Yoshiki Yazawa <yaz@honeyplanet.jp> |
|---|---|
| date | Sun, 22 Feb 2009 00:48:17 +0900 |
| parents | 63060ad65ab8 |
| children | 2e072e3d8637 |
| files | ja/intro.tex ja/todo.txt |
| diffstat | 2 files changed, 52 insertions(+), 27 deletions(-) [+] |
line wrap: on
line diff
--- a/ja/intro.tex Sat Feb 21 23:56:55 2009 +0900 +++ b/ja/intro.tex Sun Feb 22 00:48:17 2009 +0900 @@ -291,35 +291,60 @@ %\section{Trends in revision control} \section{$B%j%S%8%g%s%3%s%H%m!<%k$N%H%l%s%I(B} -There has been an unmistakable trend in the development and use of -revision control tools over the past four decades, as people have -become familiar with the capabilities of their tools and constrained -by their limitations. +%There has been an unmistakable trend in the development and use of +%revision control tools over the past four decades, as people have +%become familiar with the capabilities of their tools and constrained +%by their limitations. + +$B%j%S%8%g%s%3%s%H%m!<%k%D!<%k$N3+H/$H;HMQ$K$*$$$F!$2a5n(B20$BG/4V%D!<%k$K?F$7(B +$B$_!$%D!<%k$N@)8B$rCN$k$K=>$C$F!$J6$l$b$J$$%H%l%s%I$,B8:_$7$F$$$k!%(B -The first generation began by managing single files on individual -computers. Although these tools represented a huge advance over -ad-hoc manual revision control, their locking model and reliance on a -single computer limited them to small, tightly-knit teams. +%The first generation began by managing single files on individual +%computers. Although these tools represented a huge advance over +%ad-hoc manual revision control, their locking model and reliance on a +%single computer limited them to small, tightly-knit teams. + +$BBh0l@$Be$N%D!<%k$OC10l$N%U%!%$%k$r8DJL$N%3%s%T%e!<%?$N>e$G4IM}$7$?!%%"%I(B +$B%[%C%/$J<jF0$K$h$k%j%S%8%g%s%3%s%H%m!<%k$HHf$Y$FBgI}$J?JJb$,$"$C$?$,!$%m%C(B +$B%/%b%G%k$HC10l%3%s%T%e!<%?$X$N0MB8$N$?$a!$MxMQ$O>.5,LO$G6[L)$J%A!<%`$K8B(B +$B$i$l$?!%(B -The second generation loosened these constraints by moving to -network-centered architectures, and managing entire projects at a -time. As projects grew larger, they ran into new problems. With -clients needing to talk to servers very frequently, server scaling -became an issue for large projects. An unreliable network connection -could prevent remote users from being able to talk to the server at -all. As open source projects started making read-only access -available anonymously to anyone, people without commit privileges -found that they could not use the tools to interact with a project in -a natural way, as they could not record their changes. +%The second generation loosened these constraints by moving to +%network-centered architectures, and managing entire projects at a +%time. As projects grew larger, they ran into new problems. With +%clients needing to talk to servers very frequently, server scaling +%became an issue for large projects. An unreliable network connection +%could prevent remote users from being able to talk to the server at +%all. As open source projects started making read-only access +%available anonymously to anyone, people without commit privileges +%found that they could not use the tools to interact with a project in +%a natural way, as they could not record their changes. -The current generation of revision control tools is peer-to-peer in -nature. All of these systems have dropped the dependency on a single -central server, and allow people to distribute their revision control -data to where it's actually needed. Collaboration over the Internet -has moved from constrained by technology to a matter of choice and -consensus. Modern tools can operate offline indefinitely and -autonomously, with a network connection only needed when syncing -changes with another repository. +$BBhFs@$Be$N%D!<%k$O!$%M%C%H%o!<%/Cf?4$N%"!<%-%F%/%A%c$K0\9T$9$k$3$H$G!$$=(B +$B$l$^$G$N@)8B$r4KOB$7!$%W%m%8%'%/%HA4BN$rF1;~$K4IM}$7$?!%%W%m%8%'%/%H$,Bg(B +$B$-$/@.D9$9$k$H!$?7$?$JLdBj$KD>LL$7$?!%%/%i%$%"%s%H$,%5!<%P$KIQHK$KDL?.$9(B +$B$k$?$a!$Bg5,LO%W%m%8%'%/%H$G$O%5!<%P$N5,LO$,LdBj$K$J$C$?!%?.Mj@-$N$J$$%M%C(B +$B%H%o!<%/@\B3$O%j%b!<%H%f!<%6$,%5!<%P$HDL?.$9$k$N$rK8$2$?!%%*!<%W%s%=!<%9(B +$B%W%m%8%'%/%H$,%3%_%C%H8"$N$J$$%f!<%6$K$bF?L>$NFI$_=P$7@lMQ%"%/%;%9$rDs6!(B +$B$9$k$h$&$K$J$k$H!$%D!<%k$OH`$i$N9T$C$?JQ99$r5-O?$G$-$J$$$?$a!$%W%m%8%'%/(B +$B%H$H$d$j$H$j$r9T$&<+A3$J<jCJ$H$O8@$($J$$$3$H$,$o$+$C$?!%(B + +%The current generation of revision control tools is peer-to-peer in +%nature. All of these systems have dropped the dependency on a single +%central server, and allow people to distribute their revision control +%data to where it's actually needed. Collaboration over the Internet +%has moved from constrained by technology to a matter of choice and +%consensus. Modern tools can operate offline indefinitely and +%autonomously, with a network connection only needed when syncing +%changes with another repository. + +$B8=9T@$Be$N%j%S%8%g%s%3%s%H%m!<%k%D!<%k$O!$%T%"%D!<%T%"$G$"$k!%$3$l$i$N%7(B +$B%9%F%`$NA4$F$,C10l$NCf1{%5!<%P$X0MB8$7$J$/$J$C$F$*$j!$%j%S%8%g%s%3%s%H%m!<(B +$B%k%G!<%?$rI,MW$J$H$3$m$XJ,;6$5$;$k$3$H$,$G$-$k$h$&$K$J$C$F$$$k!%%$%s%?!<(B +$B%M%C%H$rDL$8$?6&F1:n6H$O5;=QE*@)Ls$+$iN%$l$F!$A*Br$H9g0U$K$h$C$F9T$o$l$k(B +$B$h$&$K$J$C$?!%8=Be$N%D!<%k$O%*%U%i%$%s$N$^$^$G$b!$<+N'E*$K$bF0:n$9$k$h$&(B +$B$K$J$C$F$$$k!%%M%C%H%o!<%/@\B3$OJQ99$rJL$N%j%]%8%H%j$HF14|$5$;$k;~$K$N$_(B +$BI,MW$G$"$k!%(B %\section{A few of the advantages of distributed revision control} \section{$BJ,;6%j%S%8%g%s%3%s%H%m!<%k$NMxE@(B}