| rev |
line source |
|
jerojasro@339
|
1 \chapter*{Prefacio}
|
|
jerojasro@339
|
2 \addcontentsline{toc}{chapter}{Prefacio}
|
|
jerojasro@339
|
3 \label{chap:preface}
|
|
jerojasro@339
|
4
|
|
jerojasro@339
|
5 % TODO no es mejor decir control distribuido de revisiones?
|
|
jerojasro@339
|
6 El control de revisiones distribuido es un territorio relativamente
|
|
jerojasro@339
|
7 nuevo, y ha crecido hasta ahora
|
|
jerojasro@339
|
8 % TODO el original dice "due to", que sería "debido", pero creo que "gracias
|
|
jerojasro@339
|
9 % a" queda mejor
|
|
jerojasro@339
|
10 gracias a a la voluntad que tiene la gente de salir y explorar
|
|
jerojasro@339
|
11 territorios desconocidos.
|
|
jerojasro@339
|
12 % TODO revisar la frase anterior. me tomé muchas licencias para
|
|
jerojasro@339
|
13 % traducirla
|
|
jerojasro@339
|
14
|
|
jerojasro@339
|
15 Estoy escribiendo este libro acerca de control de revisiones
|
|
jerojasro@339
|
16 distribuido porque creo que es un tema importante que merece una guía
|
|
jerojasro@339
|
17 de campo. Escogí escribir acerca de Mercurial porque es la herramienta
|
|
jerojasro@339
|
18 %TODO puse explorar en vez de aprender, you be the judge dear reviewer ;)
|
|
jerojasro@339
|
19 más fácil para explorar el terreno, y sin embargo escala a las
|
|
jerojasro@339
|
20 demandas de ambientes reales
|
|
jerojasro@339
|
21
|
|
jerojasro@339
|
22 I am writing a book about distributed revision control because I
|
|
jerojasro@339
|
23 believe that it is an important subject that deserves a field guide.
|
|
jerojasro@339
|
24 I chose to write about Mercurial because it is the easiest tool to
|
|
jerojasro@339
|
25 learn the terrain with, and yet it scales to the demands of real,
|
|
jerojasro@339
|
26 challenging environments where many other revision control tools fail.
|
|
jerojasro@339
|
27
|
|
jerojasro@339
|
28 \section{This book is a work in progress}
|
|
jerojasro@339
|
29
|
|
jerojasro@339
|
30 I am releasing this book while I am still writing it, in the hope that
|
|
jerojasro@339
|
31 it will prove useful to others. I also hope that readers will
|
|
jerojasro@339
|
32 contribute as they see fit.
|
|
jerojasro@339
|
33
|
|
jerojasro@339
|
34 \section{About the examples in this book}
|
|
jerojasro@339
|
35
|
|
jerojasro@339
|
36 This book takes an unusual approach to code samples. Every example is
|
|
jerojasro@339
|
37 ``live''---each one is actually the result of a shell script that
|
|
jerojasro@339
|
38 executes the Mercurial commands you see. Every time an image of the
|
|
jerojasro@339
|
39 book is built from its sources, all the example scripts are
|
|
jerojasro@339
|
40 automatically run, and their current results compared against their
|
|
jerojasro@339
|
41 expected results.
|
|
jerojasro@339
|
42
|
|
jerojasro@339
|
43 The advantage of this approach is that the examples are always
|
|
jerojasro@339
|
44 accurate; they describe \emph{exactly} the behaviour of the version of
|
|
jerojasro@339
|
45 Mercurial that's mentioned at the front of the book. If I update the
|
|
jerojasro@339
|
46 version of Mercurial that I'm documenting, and the output of some
|
|
jerojasro@339
|
47 command changes, the build fails.
|
|
jerojasro@339
|
48
|
|
jerojasro@339
|
49 There is a small disadvantage to this approach, which is that the
|
|
jerojasro@339
|
50 dates and times you'll see in examples tend to be ``squashed''
|
|
jerojasro@339
|
51 together in a way that they wouldn't be if the same commands were
|
|
jerojasro@339
|
52 being typed by a human. Where a human can issue no more than one
|
|
jerojasro@339
|
53 command every few seconds, with any resulting timestamps
|
|
jerojasro@339
|
54 correspondingly spread out, my automated example scripts run many
|
|
jerojasro@339
|
55 commands in one second.
|
|
jerojasro@339
|
56
|
|
jerojasro@339
|
57 As an instance of this, several consecutive commits in an example can
|
|
jerojasro@339
|
58 show up as having occurred during the same second. You can see this
|
|
jerojasro@339
|
59 occur in the \hgext{bisect} example in section~\ref{sec:undo:bisect},
|
|
jerojasro@339
|
60 for instance.
|
|
jerojasro@339
|
61
|
|
jerojasro@339
|
62 So when you're reading examples, don't place too much weight on the
|
|
jerojasro@339
|
63 dates or times you see in the output of commands. But \emph{do} be
|
|
jerojasro@339
|
64 confident that the behaviour you're seeing is consistent and
|
|
jerojasro@339
|
65 reproducible.
|
|
jerojasro@339
|
66
|
|
jerojasro@339
|
67 \section{Colophon---this book is Free}
|
|
jerojasro@339
|
68
|
|
jerojasro@339
|
69 This book is licensed under the Open Publication License, and is
|
|
jerojasro@339
|
70 produced entirely using Free Software tools. It is typeset with
|
|
jerojasro@339
|
71 \LaTeX{}; illustrations are drawn and rendered with
|
|
jerojasro@339
|
72 \href{http://www.inkscape.org/}{Inkscape}.
|
|
jerojasro@339
|
73
|
|
jerojasro@339
|
74 The complete source code for this book is published as a Mercurial
|
|
jerojasro@339
|
75 repository, at \url{http://hg.serpentine.com/mercurial/book}.
|
|
jerojasro@339
|
76
|
|
jerojasro@339
|
77 %%% Local Variables:
|
|
jerojasro@339
|
78 %%% mode: latex
|
|
jerojasro@339
|
79 %%% TeX-master: "00book"
|
|
jerojasro@339
|
80 %%% End:
|
