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