hgbook
view es/concepts.tex @ 411:006cd2b41d11
corrected translation of a term
| author | Javier Rojas <jerojasro@devnull.li> |
|---|---|
| date | Mon Nov 10 22:20:46 2008 -0500 (2008-11-10) |
| parents | 7c84967093e1 |
| children | 0eda2936ef77 |
line source
1 \chapter{Tras bambalinas}
2 \label{chap:concepts}
4 A diferencia de varios sistemas de control de revisiones, los
5 conceptos en los que se fundamenta Mercurial son lo suficientemente
6 simples como para entender fácilmente cómo funciona el software.
7 Saber esto no es necesario, pero considero útil tener un ``modelo
8 mental'' de qué es lo que sucede.
10 Comprender esto me da la confianza de que Mercurial ha sido
11 cuidadosamente diseñado para ser tanto \emph{seguro} como
12 \emph{eficiente}. Y tal vez con la misma importancia, si es fácil
13 para mí hacerme a una idea adecuada de qué está haciendo el software
14 cuando llevo a cabo una tarea relacionada con control de revisiones,
15 es menos probable que me sosprenda su comportamiento.
17 En este capítulo, cubriremos inicialmente los conceptos centrales
18 del diseño de Mercurial, y luego discutiremos algunos detalles
19 interesantes de su implementación.
21 \section{Registro del historial de Mercurial}
23 \subsection{Seguir el historial de un único fichero}
25 Cuando Mercurial sigue las modificaciones a un fichero, guarda el
26 historial de dicho fichero en un objeto de metadatos llamado
27 \emph{filelog}\ndt{Fichero de registro}. Cada entrada en el fichero
28 de registro contiene suficiente información para reconstruir una
29 revisión del fichero que se está siguiendo. Los ficheros de registro
30 son almacenados como ficheros el el directorio
31 \sdirname{.hg/store/data}. Un fichero de registro contiene dos tipos
32 de información: datos de revisiones, y un índice para ayudar a
33 Mercurial a buscar revisiones eficientemente.
35 El fichero de registro de un fichero grande, o con un historial muy
36 largo, es guardado como ficheros separados para datos (sufijo
37 ``\texttt{.d}'') y para el índice (sufijo ``\texttt{.i}''). Para
38 ficheros pequeños con un historial pequeño, los datos de revisiones y
39 el índice son combinados en un único fichero ``\texttt{.i}''. La
40 correspondencia entre un fichero en el directorio de trabajo y el
41 fichero de registro que hace seguimiento a su historial en el
42 repositorio se ilustra en la figura~\ref{fig:concepts:filelog}.
44 \begin{figure}[ht]
45 \centering
46 \grafix{filelog}
47 \caption{Relación entre ficheros en el directorio de trabajo y
48 ficheros de registro en el repositorio}
49 \label{fig:concepts:filelog}
50 \end{figure}
52 \subsection{Administración de ficheros monitoreados}
54 Mercurial usa una estructura llamada \emph{manifiesto} para
55 % TODO collect together => centralizar
56 centralizar la información que maneja acerca de los ficheros que
57 monitorea. Cada entrada en el manifiesto contiene información acerca
58 de los ficheros involucrados en un único conjunto de cambios. Una
59 entrada registra qué ficheros están presentes en el conjunto de
60 cambios, la revisión de cada fichero, y otros cuantos metadatos del
61 mismo.
63 \subsection{Registro de información del conjunto de cambios}
65 La \emph{bitácora de cambios} contiene información acerca de cada
66 conjunto de cambios. Cada revisión indica quién consignó un cambio, el
67 comentario para el conjunto de cambios, otros datos relacionados con
68 el conjunto de cambios, y la revisión del manifiesto a usar.
70 \subsection{Relaciones entre revisiones}
72 Dentro de una bitácora de cambios, un manifiesto, o un fichero de
73 registro, cada revisión conserva un apuntador a su padre inmediato
74 (o sus dos padres, si es la revisión de una fusión). Como menciońe
75 anteriormente, también hay relaciones entre revisiones \emph{a través}
76 de estas estructuras, y tienen naturaleza jerárquica.
78 Por cada conjunto de cambios en un repositorio, hay exactamente una
79 revisión almacenada en la bitácora de cambios. Cada revisión de la
80 bitácora de cambios contiene un apuntador a una única revisión del
81 manifiesto. Una revisión del manifiesto almacena un apuntador a una
82 única revisión de cada fichero de registro al que se le hacía
83 seguimiento cuando fue creado el conjunto de cambios. Estas relaciones
84 se ilustran en la figura~\ref{fig:concepts:metadata}.
86 \begin{figure}[ht]
87 \centering
88 \grafix{metadata}
89 \caption{Relaciones entre metadatos}
90 \label{fig:concepts:metadata}
91 \end{figure}
93 Como lo muestra la figura, \emph{no} hay una relación ``uno a uno''
94 entre las revisiones en el conjunto de cambios, el manifiesto, o el
95 fichero de registro. Si el manifiesto no ha sido modificado de un
96 conjunto de cambios a otro, las entradas en la bitácora de cambios
97 para esos conjuntos de cambios apuntarán a la misma revisión del
98 manifiesto. Si un fichero monitoreado por Mercurial no sufre ningún
99 cambio de un conjunto de cambios a otro, la entrada para dicho fichero
100 en las dos revisiones del manifiesto apuntará a la misma revisión de
101 su fichero de registro.
103 \section{Almacenamiento seguro y eficiente}
105 La base común de las bitácoras de cambios, los manifiestos, y los
106 ficheros de registros es provista por una única estructura llamada el
107 \emph{revlog}\ndt{Contracción de \emph{revision log}, registro de
108 revisión.}.
110 \subsection{Almacenamiento eficiente}
112 El revlog provee almacenamiento eficiente de revisiones por medio del
113 mecanismo de \emph{deltas}\ndt{Diferencias.}. En vez de almacenar una
114 copia completa del fichero por cada revisión, almacena los cambios
115 necesarios para transformar una revisión anterior en la nueva
116 revisión. Para muchos tipos de fichero, estos deltas son típicamente
117 de una fracción porcentual del tamaño de una copia completa del
118 fichero.
120 Algunos sistemas de control de revisiones obsoletos sólo pueden
121 manipular deltas de ficheros de texto plano. Ellos o bien almacenan
122 los ficheros binarios como instantáneas completas, o codificados en
123 alguna representación de texto plano adecuada, y ambas alternativas
124 son enfoques que desperdician bastantes recursos. Mercurial puede
125 manejar deltas de ficheros con contenido binario arbitrario; no
126 necesita tratar el texto plano como un caso especial.
128 \subsection{Operación segura}
129 \label{sec:concepts:txn}
131 Mercurial sólo \emph{añade} datos al final de los ficheros de revlog. Nunca
132 modifica ninguna sección de un fichero una vez ha sido escrita. Esto es más
133 robusto y eficiente que otros esquemas que requieren modificar o reescribir
134 datos.
136 Adicionalmente, Mercurial trata cada escritura como parte de una
137 \emph{transacción}, que puede cubrir varios ficheros. Una transacción es
138 \emph{atómica}: o bien la transacción tiene éxito y entonces todos sus efectos
139 son visibles para todos los lectores, o la operación completa es cancelada.
140 % TODO atomicidad no existe de acuerdo a DRAE, reemplazar
141 Esta garantía de atomicidad implica que, si usted está ejecutando dos copias de
142 Mercurial, donde una de ellas está leyendo datos y la otra los está escribiendo,
143 el lector nunca verá un resultado escrito parcialmente que podría confundirlo.
145 El hecho de que Mercurial sólo hace adiciones a los ficheros hace más fácil
146 proveer esta garantía transaccional. A medida que sea más fácil hacer
147 operaciones como ésta, más confianza tendrá usted en que sean hechas
148 correctamente.
150 \subsection{Recuperación rápida de datos}
152 Mercurial evita ingeniosamente un problema común a todos los sistemas de control
153 de revisiones anteriores> el problema de la
154 \emph{recuperación\ndt{\emph{Retrieval}. Recuperación en el sentido de traer los
155 datos, o reconstruirlos a partir de otros datos, pero no debido a una falla o
156 calamidad, sino a la operación normal del sistema.} ineficiente de datos}.
157 Muchos sistemas de control de revisiones almacenan los contenidos de una
158 revisión como una serie incremental de modificaciones a una ``instantánea''.
159 Para reconstruir una versión cualquiera, primero usted debe leer la instantánea,
160 y luego cada una de las revisiones entre la instantánea y su versión objetivo.
161 Entre más largo sea el historial de un fichero, más revisiones deben ser leídas,
162 y por tanto toma más tiempo reconstruir una versión particular.
164 \begin{figure}[ht]
165 \centering
166 \grafix{snapshot}
167 \caption{Instantánea de un revlog, con deltas incrementales}
168 \label{fig:concepts:snapshot}
169 \end{figure}
171 La innovación que aplica Mercurial a este problema es simple pero efectiva.
172 Una vez la cantidad de información de deltas acumulada desde la última
173 instantánea excede un umbral fijado de antemano, se almacena una nueva
174 instantánea (comprimida, por supuesto), en lugar de otro delta. Esto hace
175 posible reconstruir \emph{cualquier} versión de un fichero rápidamente. Este
176 enfoque funciona tan bien que desde entonces ha sido copiado por otros sistemas
177 de control de revisiones.
179 La figura~\ref{fig:concepts:snapshot} ilustra la idea. En una entrada en el
180 fichero índice de un revlog, Mercurial almacena el rango de entradas (deltas)
181 del fichero de datos que se deben leer para reconstruir una revisión en
182 particular.
184 \subsubsection{Nota al margen: la influencia de la compresión de vídeo}
186 Si le es familiar la compresión de vídeo, o ha mirado alguna vez una emisión de
187 TV a través de cable digital o un servicio de satélite, puede que sepa que la
188 mayor parte de los esquemas de compresión de vídeo almacenan cada cuadro del
189 mismo como un delta contra el cuadro predecesor. Adicionalmente, estos esquemas
190 usan técnicas de compresión ``con pérdida'' para aumentar la tasa de
191 compresión, por lo que los errores visuales se acumulan a lo largo de una
192 cantidad de deltas inter-cuadros.
194 Because it's possible for a video stream to ``drop out'' occasionally
195 due to signal glitches, and to limit the accumulation of artefacts
196 introduced by the lossy compression process, video encoders
197 periodically insert a complete frame (called a ``key frame'') into the
198 video stream; the next delta is generated against that frame. This
199 means that if the video signal gets interrupted, it will resume once
200 the next key frame is received. Also, the accumulation of encoding
201 errors restarts anew with each key frame.
203 \subsection{Identification and strong integrity}
205 Along with delta or snapshot information, a revlog entry contains a
206 cryptographic hash of the data that it represents. This makes it
207 difficult to forge the contents of a revision, and easy to detect
208 accidental corruption.
210 Hashes provide more than a mere check against corruption; they are
211 used as the identifiers for revisions. The changeset identification
212 hashes that you see as an end user are from revisions of the
213 changelog. Although filelogs and the manifest also use hashes,
214 Mercurial only uses these behind the scenes.
216 Mercurial verifies that hashes are correct when it retrieves file
217 revisions and when it pulls changes from another repository. If it
218 encounters an integrity problem, it will complain and stop whatever
219 it's doing.
221 In addition to the effect it has on retrieval efficiency, Mercurial's
222 use of periodic snapshots makes it more robust against partial data
223 corruption. If a revlog becomes partly corrupted due to a hardware
224 error or system bug, it's often possible to reconstruct some or most
225 revisions from the uncorrupted sections of the revlog, both before and
226 after the corrupted section. This would not be possible with a
227 delta-only storage model.
229 \section{Revision history, branching,
230 and merging}
232 Every entry in a Mercurial revlog knows the identity of its immediate
233 ancestor revision, usually referred to as its \emph{parent}. In fact,
234 a revision contains room for not one parent, but two. Mercurial uses
235 a special hash, called the ``null ID'', to represent the idea ``there
236 is no parent here''. This hash is simply a string of zeroes.
238 In figure~\ref{fig:concepts:revlog}, you can see an example of the
239 conceptual structure of a revlog. Filelogs, manifests, and changelogs
240 all have this same structure; they differ only in the kind of data
241 stored in each delta or snapshot.
243 The first revision in a revlog (at the bottom of the image) has the
244 null ID in both of its parent slots. For a ``normal'' revision, its
245 first parent slot contains the ID of its parent revision, and its
246 second contains the null ID, indicating that the revision has only one
247 real parent. Any two revisions that have the same parent ID are
248 branches. A revision that represents a merge between branches has two
249 normal revision IDs in its parent slots.
251 \begin{figure}[ht]
252 \centering
253 \grafix{revlog}
254 \caption{}
255 \label{fig:concepts:revlog}
256 \end{figure}
258 \section{The working directory}
260 In the working directory, Mercurial stores a snapshot of the files
261 from the repository as of a particular changeset.
263 The working directory ``knows'' which changeset it contains. When you
264 update the working directory to contain a particular changeset,
265 Mercurial looks up the appropriate revision of the manifest to find
266 out which files it was tracking at the time that changeset was
267 committed, and which revision of each file was then current. It then
268 recreates a copy of each of those files, with the same contents it had
269 when the changeset was committed.
271 The \emph{dirstate} contains Mercurial's knowledge of the working
272 directory. This details which changeset the working directory is
273 updated to, and all of the files that Mercurial is tracking in the
274 working directory.
276 Just as a revision of a revlog has room for two parents, so that it
277 can represent either a normal revision (with one parent) or a merge of
278 two earlier revisions, the dirstate has slots for two parents. When
279 you use the \hgcmd{update} command, the changeset that you update to
280 is stored in the ``first parent'' slot, and the null ID in the second.
281 When you \hgcmd{merge} with another changeset, the first parent
282 remains unchanged, and the second parent is filled in with the
283 changeset you're merging with. The \hgcmd{parents} command tells you
284 what the parents of the dirstate are.
286 \subsection{What happens when you commit}
288 The dirstate stores parent information for more than just book-keeping
289 purposes. Mercurial uses the parents of the dirstate as \emph{the
290 parents of a new changeset} when you perform a commit.
292 \begin{figure}[ht]
293 \centering
294 \grafix{wdir}
295 \caption{The working directory can have two parents}
296 \label{fig:concepts:wdir}
297 \end{figure}
299 Figure~\ref{fig:concepts:wdir} shows the normal state of the working
300 directory, where it has a single changeset as parent. That changeset
301 is the \emph{tip}, the newest changeset in the repository that has no
302 children.
304 \begin{figure}[ht]
305 \centering
306 \grafix{wdir-after-commit}
307 \caption{The working directory gains new parents after a commit}
308 \label{fig:concepts:wdir-after-commit}
309 \end{figure}
311 It's useful to think of the working directory as ``the changeset I'm
312 about to commit''. Any files that you tell Mercurial that you've
313 added, removed, renamed, or copied will be reflected in that
314 changeset, as will modifications to any files that Mercurial is
315 already tracking; the new changeset will have the parents of the
316 working directory as its parents.
318 After a commit, Mercurial will update the parents of the working
319 directory, so that the first parent is the ID of the new changeset,
320 and the second is the null ID. This is shown in
321 figure~\ref{fig:concepts:wdir-after-commit}. Mercurial doesn't touch
322 any of the files in the working directory when you commit; it just
323 modifies the dirstate to note its new parents.
325 \subsection{Creating a new head}
327 It's perfectly normal to update the working directory to a changeset
328 other than the current tip. For example, you might want to know what
329 your project looked like last Tuesday, or you could be looking through
330 changesets to see which one introduced a bug. In cases like this, the
331 natural thing to do is update the working directory to the changeset
332 you're interested in, and then examine the files in the working
333 directory directly to see their contents as they werea when you
334 committed that changeset. The effect of this is shown in
335 figure~\ref{fig:concepts:wdir-pre-branch}.
337 \begin{figure}[ht]
338 \centering
339 \grafix{wdir-pre-branch}
340 \caption{The working directory, updated to an older changeset}
341 \label{fig:concepts:wdir-pre-branch}
342 \end{figure}
344 Having updated the working directory to an older changeset, what
345 happens if you make some changes, and then commit? Mercurial behaves
346 in the same way as I outlined above. The parents of the working
347 directory become the parents of the new changeset. This new changeset
348 has no children, so it becomes the new tip. And the repository now
349 contains two changesets that have no children; we call these
350 \emph{heads}. You can see the structure that this creates in
351 figure~\ref{fig:concepts:wdir-branch}.
353 \begin{figure}[ht]
354 \centering
355 \grafix{wdir-branch}
356 \caption{After a commit made while synced to an older changeset}
357 \label{fig:concepts:wdir-branch}
358 \end{figure}
360 \begin{note}
361 If you're new to Mercurial, you should keep in mind a common
362 ``error'', which is to use the \hgcmd{pull} command without any
363 options. By default, the \hgcmd{pull} command \emph{does not}
364 update the working directory, so you'll bring new changesets into
365 your repository, but the working directory will stay synced at the
366 same changeset as before the pull. If you make some changes and
367 commit afterwards, you'll thus create a new head, because your
368 working directory isn't synced to whatever the current tip is.
370 I put the word ``error'' in quotes because all that you need to do
371 to rectify this situation is \hgcmd{merge}, then \hgcmd{commit}. In
372 other words, this almost never has negative consequences; it just
373 surprises people. I'll discuss other ways to avoid this behaviour,
374 and why Mercurial behaves in this initially surprising way, later
375 on.
376 \end{note}
378 \subsection{Merging heads}
380 When you run the \hgcmd{merge} command, Mercurial leaves the first
381 parent of the working directory unchanged, and sets the second parent
382 to the changeset you're merging with, as shown in
383 figure~\ref{fig:concepts:wdir-merge}.
385 \begin{figure}[ht]
386 \centering
387 \grafix{wdir-merge}
388 \caption{Merging two heads}
389 \label{fig:concepts:wdir-merge}
390 \end{figure}
392 Mercurial also has to modify the working directory, to merge the files
393 managed in the two changesets. Simplified a little, the merging
394 process goes like this, for every file in the manifests of both
395 changesets.
396 \begin{itemize}
397 \item If neither changeset has modified a file, do nothing with that
398 file.
399 \item If one changeset has modified a file, and the other hasn't,
400 create the modified copy of the file in the working directory.
401 \item If one changeset has removed a file, and the other hasn't (or
402 has also deleted it), delete the file from the working directory.
403 \item If one changeset has removed a file, but the other has modified
404 the file, ask the user what to do: keep the modified file, or remove
405 it?
406 \item If both changesets have modified a file, invoke an external
407 merge program to choose the new contents for the merged file. This
408 may require input from the user.
409 \item If one changeset has modified a file, and the other has renamed
410 or copied the file, make sure that the changes follow the new name
411 of the file.
412 \end{itemize}
413 There are more details---merging has plenty of corner cases---but
414 these are the most common choices that are involved in a merge. As
415 you can see, most cases are completely automatic, and indeed most
416 merges finish automatically, without requiring your input to resolve
417 any conflicts.
419 When you're thinking about what happens when you commit after a merge,
420 once again the working directory is ``the changeset I'm about to
421 commit''. After the \hgcmd{merge} command completes, the working
422 directory has two parents; these will become the parents of the new
423 changeset.
425 Mercurial lets you perform multiple merges, but you must commit the
426 results of each individual merge as you go. This is necessary because
427 Mercurial only tracks two parents for both revisions and the working
428 directory. While it would be technically possible to merge multiple
429 changesets at once, the prospect of user confusion and making a
430 terrible mess of a merge immediately becomes overwhelming.
432 \section{Other interesting design features}
434 In the sections above, I've tried to highlight some of the most
435 important aspects of Mercurial's design, to illustrate that it pays
436 careful attention to reliability and performance. However, the
437 attention to detail doesn't stop there. There are a number of other
438 aspects of Mercurial's construction that I personally find
439 interesting. I'll detail a few of them here, separate from the ``big
440 ticket'' items above, so that if you're interested, you can gain a
441 better idea of the amount of thinking that goes into a well-designed
442 system.
444 \subsection{Clever compression}
446 When appropriate, Mercurial will store both snapshots and deltas in
447 compressed form. It does this by always \emph{trying to} compress a
448 snapshot or delta, but only storing the compressed version if it's
449 smaller than the uncompressed version.
451 This means that Mercurial does ``the right thing'' when storing a file
452 whose native form is compressed, such as a \texttt{zip} archive or a
453 JPEG image. When these types of files are compressed a second time,
454 the resulting file is usually bigger than the once-compressed form,
455 and so Mercurial will store the plain \texttt{zip} or JPEG.
457 Deltas between revisions of a compressed file are usually larger than
458 snapshots of the file, and Mercurial again does ``the right thing'' in
459 these cases. It finds that such a delta exceeds the threshold at
460 which it should store a complete snapshot of the file, so it stores
461 the snapshot, again saving space compared to a naive delta-only
462 approach.
464 \subsubsection{Network recompression}
466 When storing revisions on disk, Mercurial uses the ``deflate''
467 compression algorithm (the same one used by the popular \texttt{zip}
468 archive format), which balances good speed with a respectable
469 compression ratio. However, when transmitting revision data over a
470 network connection, Mercurial uncompresses the compressed revision
471 data.
473 If the connection is over HTTP, Mercurial recompresses the entire
474 stream of data using a compression algorithm that gives a better
475 compression ratio (the Burrows-Wheeler algorithm from the widely used
476 \texttt{bzip2} compression package). This combination of algorithm
477 and compression of the entire stream (instead of a revision at a time)
478 substantially reduces the number of bytes to be transferred, yielding
479 better network performance over almost all kinds of network.
481 (If the connection is over \command{ssh}, Mercurial \emph{doesn't}
482 recompress the stream, because \command{ssh} can already do this
483 itself.)
485 \subsection{Read/write ordering and atomicity}
487 Appending to files isn't the whole story when it comes to guaranteeing
488 that a reader won't see a partial write. If you recall
489 figure~\ref{fig:concepts:metadata}, revisions in the changelog point to
490 revisions in the manifest, and revisions in the manifest point to
491 revisions in filelogs. This hierarchy is deliberate.
493 A writer starts a transaction by writing filelog and manifest data,
494 and doesn't write any changelog data until those are finished. A
495 reader starts by reading changelog data, then manifest data, followed
496 by filelog data.
498 Since the writer has always finished writing filelog and manifest data
499 before it writes to the changelog, a reader will never read a pointer
500 to a partially written manifest revision from the changelog, and it will
501 never read a pointer to a partially written filelog revision from the
502 manifest.
504 \subsection{Concurrent access}
506 The read/write ordering and atomicity guarantees mean that Mercurial
507 never needs to \emph{lock} a repository when it's reading data, even
508 if the repository is being written to while the read is occurring.
509 This has a big effect on scalability; you can have an arbitrary number
510 of Mercurial processes safely reading data from a repository safely
511 all at once, no matter whether it's being written to or not.
513 The lockless nature of reading means that if you're sharing a
514 repository on a multi-user system, you don't need to grant other local
515 users permission to \emph{write} to your repository in order for them
516 to be able to clone it or pull changes from it; they only need
517 \emph{read} permission. (This is \emph{not} a common feature among
518 revision control systems, so don't take it for granted! Most require
519 readers to be able to lock a repository to access it safely, and this
520 requires write permission on at least one directory, which of course
521 makes for all kinds of nasty and annoying security and administrative
522 problems.)
524 Mercurial uses locks to ensure that only one process can write to a
525 repository at a time (the locking mechanism is safe even over
526 filesystems that are notoriously hostile to locking, such as NFS). If
527 a repository is locked, a writer will wait for a while to retry if the
528 repository becomes unlocked, but if the repository remains locked for
529 too long, the process attempting to write will time out after a while.
530 This means that your daily automated scripts won't get stuck forever
531 and pile up if a system crashes unnoticed, for example. (Yes, the
532 timeout is configurable, from zero to infinity.)
534 \subsubsection{Safe dirstate access}
536 As with revision data, Mercurial doesn't take a lock to read the
537 dirstate file; it does acquire a lock to write it. To avoid the
538 possibility of reading a partially written copy of the dirstate file,
539 Mercurial writes to a file with a unique name in the same directory as
540 the dirstate file, then renames the temporary file atomically to
541 \filename{dirstate}. The file named \filename{dirstate} is thus
542 guaranteed to be complete, not partially written.
544 \subsection{Avoiding seeks}
546 Critical to Mercurial's performance is the avoidance of seeks of the
547 disk head, since any seek is far more expensive than even a
548 comparatively large read operation.
550 This is why, for example, the dirstate is stored in a single file. If
551 there were a dirstate file per directory that Mercurial tracked, the
552 disk would seek once per directory. Instead, Mercurial reads the
553 entire single dirstate file in one step.
555 Mercurial also uses a ``copy on write'' scheme when cloning a
556 repository on local storage. Instead of copying every revlog file
557 from the old repository into the new repository, it makes a ``hard
558 link'', which is a shorthand way to say ``these two names point to the
559 same file''. When Mercurial is about to write to one of a revlog's
560 files, it checks to see if the number of names pointing at the file is
561 greater than one. If it is, more than one repository is using the
562 file, so Mercurial makes a new copy of the file that is private to
563 this repository.
565 A few revision control developers have pointed out that this idea of
566 making a complete private copy of a file is not very efficient in its
567 use of storage. While this is true, storage is cheap, and this method
568 gives the highest performance while deferring most book-keeping to the
569 operating system. An alternative scheme would most likely reduce
570 performance and increase the complexity of the software, each of which
571 is much more important to the ``feel'' of day-to-day use.
573 \subsection{Other contents of the dirstate}
575 Because Mercurial doesn't force you to tell it when you're modifying a
576 file, it uses the dirstate to store some extra information so it can
577 determine efficiently whether you have modified a file. For each file
578 in the working directory, it stores the time that it last modified the
579 file itself, and the size of the file at that time.
581 When you explicitly \hgcmd{add}, \hgcmd{remove}, \hgcmd{rename} or
582 \hgcmd{copy} files, Mercurial updates the dirstate so that it knows
583 what to do with those files when you commit.
585 When Mercurial is checking the states of files in the working
586 directory, it first checks a file's modification time. If that has
587 not changed, the file must not have been modified. If the file's size
588 has changed, the file must have been modified. If the modification
589 time has changed, but the size has not, only then does Mercurial need
590 to read the actual contents of the file to see if they've changed.
591 Storing these few extra pieces of information dramatically reduces the
592 amount of data that Mercurial needs to read, which yields large
593 performance improvements compared to other revision control systems.
595 %%% Local Variables:
596 %%% mode: latex
597 %%% TeX-master: "00book"
598 %%% End: