hgbook
diff en/undo.tex @ 200:9bba958be4c6
Mention automatic example generation.
author | Bryan O'Sullivan <bos@serpentine.com> |
---|---|
date | Wed Apr 18 11:55:39 2007 -0700 (2007-04-18) |
parents | 153efeaa8f57 |
children | 80fc720338a5 |
line diff
1.1 --- a/en/undo.tex Thu Dec 28 14:10:23 2006 -0800 1.2 +++ b/en/undo.tex Wed Apr 18 11:55:39 2007 -0700 1.3 @@ -26,7 +26,9 @@ 1.4 each modification of a repository as a \emph{transaction}. Every time 1.5 you commit a changeset or pull changes from another repository, 1.6 Mercurial remembers what you did. You can undo, or \emph{roll back}, 1.7 -exactly one of these actions using the \hgcmd{rollback} command. 1.8 +exactly one of these actions using the \hgcmd{rollback} command. (See 1.9 +section~\ref{sec:undo:rollback-after-push} for an important caveat 1.10 +about the use of this command.) 1.11 1.12 Here's a mistake that I often find myself making: committing a change 1.13 in which I've created a new file, but forgotten to \hgcmd{add} it. 1.14 @@ -77,6 +79,7 @@ 1.15 all you need to undo this mistake. 1.16 1.17 \subsection{Rolling back is useless once you've pushed} 1.18 +\label{sec:undo:rollback-after-push} 1.19 1.20 The value of the \hgcmd{rollback} command drops to zero once you've 1.21 pushed your changes to another repository. Rolling back a change 1.22 @@ -455,6 +458,7 @@ 1.23 changesets. Kind of an important omission. 1.24 1.25 \section{Finding the source of a bug} 1.26 +\label{sec:undo:bisect} 1.27 1.28 While it's all very well to be able to back out a changeset that 1.29 introduced a bug, this requires that you know which changeset to back