changeset 128:98ba6ac8ac93

learning in workflows: renamed sysadmin workflow to 'log keeping'
author Arne Babenhauserheide <bab@draketo.de>
date Fri, 01 May 2009 13:54:03 +0200
parents ac97975760a7
children 177b4120c26b
files text/learning_mercurial_in_workflows.txt
diffstat 1 files changed, 3 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/text/learning_mercurial_in_workflows.txt	Fri May 01 13:52:06 2009 +0200
+++ b/text/learning_mercurial_in_workflows.txt	Fri May 01 13:54:03 2009 +0200
@@ -6,15 +6,13 @@
 
 = Basic workflows =
 
-== Sysadmin workflow ==
+== Log keeping ==
 
 === Use Case ===
 
-The first workflow is also the easiest one: You're a sysadmin and you want to use Mercurial to be able to look back when you did which changes. 
+The first workflow is also the easiest one: You want to use Mercurial to be able to look back when you did which changes. 
 
-This workflow only requires an installed Mercurial and write access to some file storage (you almost definitely have that :) ). It shows the basic technics for more complex workflows. 
-
-Note: The name doesn't mean that every sysadmin will only need this simple workflow. It was chosen in honor of a [mail]() which reminded us, that this simple usage is already a workflow in its own right. 
+This workflow only requires an installed Mercurial and write access to some file storage (you almost definitely have that :) ). It shows the basic techniques for more complex workflows. 
 
 === Workflow ===