Complete Mercurial Branching Strategy

(Arne Babenhauserheide)
2013-01-20: update image links

update image links

diff --git a/workflow.txt b/workflow.txt
--- a/workflow.txt
+++ b/workflow.txt
@@ -40,7 +40,7 @@ To visualize the structure, here’s a 3
 
 [^verification]: Those users who want external verification can restrict themselves to the tagged releases - potentially [GPG signed](http://mercurial.selenic.com/wiki/GpgExtension) by trusted 3rd-party reviewers. GPG signatures are treated like hotfixes: reviewers sign on stable (via `hg sign` without options) and merge into default. Signing directly on stable reduces the possibility of signing the wrong revision.
 
-> [![Overview Diagram](/files/hgbranchingoverview_2.png)](/files/2012-09-03-Mo-hg-branching-diagrams_12.org)  
+> [![Overview Diagram](/files/hgbranchingoverview_2.png)](/files/2012-09-03-Mo-hg-branching-diagrams_13.org)  
 > An overview of the branching strategy. Click the image to get the [emacs](/light/english/emacs) [org-mode](http://orgmode.org) [ditaa](http://ditaa.sourceforge.net/)-source.
 
 ## Practial Actions
@@ -537,7 +537,7 @@ With this merge-chain you don’t need s
 
 In the [Diagram](#diagram) this just adds a merge path from the hotfix to the still maintained releases.
 
-> [![Overview Diagram](/files/hgbranchingmaintain_2.png)](/files/2012-09-03-Mo-hg-branching-diagrams_12.org)  
+> [![Overview Diagram](/files/hgbranchingmaintain_3.png)](/files/2012-09-03-Mo-hg-branching-diagrams_13.org)  
 > An overview of the branching strategy with maintained releases. Click the image to get the [emacs](/light/english/emacs) [org-mode](http://orgmode.org) [ditaa](http://ditaa.sourceforge.net/)-source.
 
 <a name="graft-releases"></a>
@@ -617,7 +617,7 @@ The history now looks like this[^graftre
 
 In the [Diagram](#diagram) this just adds graft commits to stable:
 
-> [![Overview Diagram](/files/hgbranchinggraft_3.png)](/files/2012-09-03-Mo-hg-branching-diagrams_12.org)  
+> [![Overview Diagram](/files/hgbranchinggraft_3.png)](/files/2012-09-03-Mo-hg-branching-diagrams_13.org)  
 > An overview of the branching strategy with grafted micro-releases. Click the image to get the [emacs](/light/english/emacs) [org-mode](http://orgmode.org) [ditaa](http://ditaa.sourceforge.net/)-source.
 
 Grafted micro-releases add another layer between development and releases. They can be necessary in cases where testing requires actually deploying a release, as for example in [Freenet](http://freenetproject.org).
@@ -643,7 +643,7 @@ A special condition when using a review 
 
 In the [Diagram](#diagram) this just adds the `review` branch between `default` and `stable` instead of the release merge. Also it adds the hotfix merge to the `review` branch. 
 
-> [![Overview Diagram](/files/hgbranchingreview.png)](/files/2012-09-03-Mo-hg-branching-diagrams_12.org)  
+> [![Overview Diagram](/files/hgbranchingreview.png)](/files/2012-09-03-Mo-hg-branching-diagrams_13.org)  
 > An overview of the branching strategy with a `review` branch. Click the image to get the [emacs](/light/english/emacs) [org-mode](http://orgmode.org) [ditaa](http://ditaa.sourceforge.net/)-source.