# HG changeset patch # User Arne Babenhauserheide # Date 1242109824 -7200 # Node ID 53e4007ac24fd278d18ee7a4dbf9a8dd9aea922a # Parent 1a01a60eeaf556e742cb3bc2376ab8d6b2fcfdda Fix: the first workflow was called sysadmin instead of the (now) correct 'log keeping'. diff -r 1a01a60eeaf5 -r 53e4007ac24f hgscm/templates/workflow_guide.html --- a/hgscm/templates/workflow_guide.html Tue May 12 08:28:27 2009 +0200 +++ b/hgscm/templates/workflow_guide.html Tue May 12 08:30:24 2009 +0200 @@ -104,7 +104,7 @@ The second workflow is still very easy: You're a lone developer and you want to use Mercurial to keep track of your own changes. -It works just like the sysadmin workflow, with the difference that you go back to earlied changes at times. +It works just like the log keeping workflow, with the difference that you go back to earlied changes at times. To start a new project, you initialize a repository, add your files and commit whenever you finished a part of your work. @@ -129,7 +129,7 @@
Seeing an earlier revision
-Different from the sysadmin workflow, you'll want to go back in history at times and undo some changes, for example because it introduced a bug. +Different from the log keeping workflow, you'll want to go back in history at times and undo some changes, for example because it introduced a bug. To look at a previous version of your code, you can use update. Let's assume that you want to see revision 3.