Mercurial > hgbook
comparison en/ch08-undo.xml @ 771:b338f5490029
Americanize spellings :-(
| author | Bryan O'Sullivan <bos@serpentine.com> |
|---|---|
| date | Thu, 09 Apr 2009 22:52:16 -0700 |
| parents | 1c13ed2130a7 |
| children | 7226e5e750a6 |
comparison
equal
deleted
inserted
replaced
| 770:eb11ec9eed8c | 771:b338f5490029 |
|---|---|
| 149 <para id="x_e0">Mercurial stores exactly one transaction in its | 149 <para id="x_e0">Mercurial stores exactly one transaction in its |
| 150 transaction log; that transaction is the most recent one that | 150 transaction log; that transaction is the most recent one that |
| 151 occurred in the repository. This means that you can only roll | 151 occurred in the repository. This means that you can only roll |
| 152 back one transaction. If you expect to be able to roll back | 152 back one transaction. If you expect to be able to roll back |
| 153 one transaction, then its predecessor, this is not the | 153 one transaction, then its predecessor, this is not the |
| 154 behaviour you will get.</para> | 154 behavior you will get.</para> |
| 155 | 155 |
| 156 &interaction.rollback.twice; | 156 &interaction.rollback.twice; |
| 157 | 157 |
| 158 <para id="x_e1">Once you've rolled back one transaction in a repository, | 158 <para id="x_e1">Once you've rolled back one transaction in a repository, |
| 159 you can't roll back again in that repository until you perform | 159 you can't roll back again in that repository until you perform |
| 686 helps you to automate this process and accomplish it very | 686 helps you to automate this process and accomplish it very |
| 687 efficiently.</para> | 687 efficiently.</para> |
| 688 | 688 |
| 689 <para id="x_127">The idea behind the <command role="hg-cmd">hg | 689 <para id="x_127">The idea behind the <command role="hg-cmd">hg |
| 690 bisect</command> command is that a changeset has introduced | 690 bisect</command> command is that a changeset has introduced |
| 691 some change of behaviour that you can identify with a simple | 691 some change of behavior that you can identify with a simple |
| 692 binary test. You don't know which piece of code introduced the | 692 binary test. You don't know which piece of code introduced the |
| 693 change, but you know how to test for the presence of the bug. | 693 change, but you know how to test for the presence of the bug. |
| 694 The <command role="hg-cmd">hg bisect</command> command uses your | 694 The <command role="hg-cmd">hg bisect</command> command uses your |
| 695 test to direct its search for the changeset that introduced the | 695 test to direct its search for the changeset that introduced the |
| 696 code that caused the bug.</para> | 696 code that caused the bug.</para> |
| 1054 | 1054 |
| 1055 <para id="x_15c">Even if you end up <quote>early</quote> by thousands of | 1055 <para id="x_15c">Even if you end up <quote>early</quote> by thousands of |
| 1056 changesets or months of history, you will only add a handful | 1056 changesets or months of history, you will only add a handful |
| 1057 of tests to the total number that <command role="hg-cmd">hg | 1057 of tests to the total number that <command role="hg-cmd">hg |
| 1058 bisect</command> must perform, thanks to its logarithmic | 1058 bisect</command> must perform, thanks to its logarithmic |
| 1059 behaviour.</para> | 1059 behavior.</para> |
| 1060 | 1060 |
| 1061 </sect2> | 1061 </sect2> |
| 1062 </sect1> | 1062 </sect1> |
| 1063 </chapter> | 1063 </chapter> |
| 1064 | 1064 |