hgbook
diff es/concepts.tex @ 393:2c2c86824c61
began translation of the "behind the scenes" chapter
author | Javier Rojas <jerojasro@devnull.li> |
---|---|
date | Mon Nov 03 21:00:32 2008 -0500 (2008-11-03) |
parents | 2fb78d342e07 |
children | 149ea8ae39c4 |
line diff
1.1 --- a/es/concepts.tex Sun Oct 19 19:56:21 2008 -0500 1.2 +++ b/es/concepts.tex Mon Nov 03 21:00:32 2008 -0500 1.3 @@ -1,26 +1,29 @@ 1.4 -\chapter{Behind the scenes} 1.5 +\chapter{Tras bambalinas} 1.6 \label{chap:concepts} 1.7 1.8 -Unlike many revision control systems, the concepts upon which 1.9 -Mercurial is built are simple enough that it's easy to understand how 1.10 -the software really works. Knowing this certainly isn't necessary, 1.11 -but I find it useful to have a ``mental model'' of what's going on. 1.12 - 1.13 -This understanding gives me confidence that Mercurial has been 1.14 -carefully designed to be both \emph{safe} and \emph{efficient}. And 1.15 -just as importantly, if it's easy for me to retain a good idea of what 1.16 -the software is doing when I perform a revision control task, I'm less 1.17 -likely to be surprised by its behaviour. 1.18 - 1.19 -In this chapter, we'll initially cover the core concepts behind 1.20 -Mercurial's design, then continue to discuss some of the interesting 1.21 -details of its implementation. 1.22 - 1.23 -\section{Mercurial's historical record} 1.24 - 1.25 -\subsection{Tracking the history of a single file} 1.26 - 1.27 -When Mercurial tracks modifications to a file, it stores the history 1.28 +A diferencia de varios sistemas de control de revisiones, los 1.29 +conceptos en los que se fundamenta Mercurial son lo suficientemente 1.30 +simples como para entender fácilmente cómo funciona el software. 1.31 +Saber esto no es necesario, pero considero útil tener un ``modelo 1.32 +mental'' de qué es lo que sucede. 1.33 + 1.34 +Comprender esto me da la confianza de que Mercurial ha sido 1.35 +cuidadosamente diseñado para ser tanto \emph{seguro} como 1.36 +\emph{eficiente}. Y tal vez con la misma importancia, si es fácil 1.37 +para mí hacerme a una idea adecuada de qué está haciendo el software 1.38 +cuando llevo a cabo una tarea relacionada con control de revisiones, 1.39 +es menos probable que me sosprenda su comportamiento. 1.40 + 1.41 +En este capítulo, cubriremos inicialmente los conceptos centrales 1.42 +del diseño de Mercurial, y luego discutiremos algunos detalles 1.43 +interesantes de su implementación. 1.44 + 1.45 +\section{Registro del historial de Mercurial} 1.46 + 1.47 +\subsection{Seguir el historial de un único fichero} 1.48 + 1.49 +Cuando Mercurial sigue las modificaciones a un fichero, guarda el 1.50 +historial de dicho fichero en un objeto de metadatos llamado 1.51 of that file in a metadata object called a \emph{filelog}. Each entry 1.52 in the filelog contains enough information to reconstruct one revision 1.53 of the file that is being tracked. Filelogs are stored as files in