Mercurial > hg-website
changeset 153:53e4007ac24f
Fix: the first workflow was called sysadmin instead of the (now) correct 'log keeping'.
| author | Arne Babenhauserheide <bab@draketo.de> |
|---|---|
| date | Tue, 12 May 2009 08:30:24 +0200 |
| parents | 1a01a60eeaf5 |
| children | 08f4b19d865e |
| files | hgscm/templates/workflow_guide.html |
| diffstat | 1 files changed, 2 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- 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 @@ <h5>Seeing an earlier revision</h5> -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.