diff options
| author | Owen Jacobson <owen.jacobson@grimoire.ca> | 2015-07-17 01:30:44 -0400 |
|---|---|---|
| committer | Owen Jacobson <owen.jacobson@grimoire.ca> | 2015-07-17 01:32:37 -0400 |
| commit | 79a5ee985199c7b12392ef168a042309b6fa4e29 (patch) | |
| tree | 97236a7f25480cb6a2f5b441cb370e1fa7b61b76 /wiki | |
| parent | 76aed6ef732de38d82245b3d674f70bab30221e5 (diff) | |
Fixup image links for Dokku-based version of site.
Diffstat (limited to 'wiki')
| -rw-r--r-- | wiki/dev/builds.md | 2 | ||||
| -rw-r--r-- | wiki/dev/merging-structural-changes.md | 6 | ||||
| -rw-r--r-- | wiki/email.md | 2 |
3 files changed, 5 insertions, 5 deletions
diff --git a/wiki/dev/builds.md b/wiki/dev/builds.md index 8f334a1..abe3d19 100644 --- a/wiki/dev/builds.md +++ b/wiki/dev/builds.md @@ -37,7 +37,7 @@ person—“creativity,” “morality,” “curiosity,” and so on. Extensible. Understood. In the middle tier: Simple. Fast. Unit tests. Part of the project. Environment independent. At the top: Metrics. Parallel builds. Acceptance tests. Product caching. IDE -integration.](/media/dev/builds/buildifesto-pyramid) +integration.](/media/dev/builds/buildifesto-pyramid.png) Builds, and software engineering as a whole, can be described the same way: at the top of the hierarchy is a working system that solves a problem, and at the diff --git a/wiki/dev/merging-structural-changes.md b/wiki/dev/merging-structural-changes.md index a47fdcc..d1c7a9c 100644 --- a/wiki/dev/merging-structural-changes.md +++ b/wiki/dev/merging-structural-changes.md @@ -17,7 +17,7 @@ changes when merging structural changes to the same files. ## The Preferred Outcome  +merge.](/media/dev/merging-structural-changes/ideal-merge-results.png) The diagram above shows a very simple source tree with one directory, `dir-a`, containing one file with two lines in it. On one branch, the file is modified @@ -31,7 +31,7 @@ merging. ## Subversion  +change.](/media/dev/merging-structural-changes/subversion-merge-results.png) There are two merge scenarios in this diagram, with almost the same outcome. On the left, a working copy of the branch where the file's content changed is @@ -69,7 +69,7 @@ ignoring changes. ## Mercurial  +change.](/media/dev/merging-structural-changes/mercurial-merge-results.png) Interestingly, there are tools which get this merge scenario right: the diagram above shows how [Mercurial](http://www.selenic.com/mercurial/) handles diff --git a/wiki/email.md b/wiki/email.md index d7450eb..53350a8 100644 --- a/wiki/email.md +++ b/wiki/email.md @@ -3,7 +3,7 @@  +yes, then read immediately. If no, UNREAD FOREVER.](/media/email/flowchart.png) I get a lot of email, often while I'm in [the middle of something thought-intensive](http://blog.ninlabs.com/2013/01/programmer-interrupted/). |