diff en/undo.tex @ 200:9bba958be4c6

Mention automatic example generation.
author Bryan O'Sullivan <bos@serpentine.com>
date Wed, 18 Apr 2007 11:55:39 -0700
parents 153efeaa8f57
children 80fc720338a5
line wrap: on
line diff
--- a/en/undo.tex	Mon Apr 16 17:37:27 2007 -0700
+++ b/en/undo.tex	Wed Apr 18 11:55:39 2007 -0700
@@ -26,7 +26,9 @@
 each modification of a repository as a \emph{transaction}.  Every time
 you commit a changeset or pull changes from another repository,
 Mercurial remembers what you did.  You can undo, or \emph{roll back},
-exactly one of these actions using the \hgcmd{rollback} command.
+exactly one of these actions using the \hgcmd{rollback} command.  (See
+section~\ref{sec:undo:rollback-after-push} for an important caveat
+about the use of this command.)
 
 Here's a mistake that I often find myself making: committing a change
 in which I've created a new file, but forgotten to \hgcmd{add} it.
@@ -77,6 +79,7 @@
 all you need to undo this mistake.
 
 \subsection{Rolling back is useless once you've pushed}
+\label{sec:undo:rollback-after-push}
 
 The value of the \hgcmd{rollback} command drops to zero once you've
 pushed your changes to another repository.  Rolling back a change
@@ -455,6 +458,7 @@
 changesets.  Kind of an important omission.
 
 \section{Finding the source of a bug}
+\label{sec:undo:bisect}
 
 While it's all very well to be able to back out a changeset that
 introduced a bug, this requires that you know which changeset to back