summaryrefslogtreecommitdiff
path: root/wiki
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-03 14:39:28 -0500
committerOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-03 14:39:28 -0500
commit35c66248fdb61c13e54fd50b06b93823fdf8f4fe (patch)
treeb131d33f64f49260f766abb8b85bf9e1c9f7f04f /wiki
parent750b4ee0732d89d2e1595436feab1b4d3b765673 (diff)
Pointers to GitHub history.
Diffstat (limited to 'wiki')
-rw-r--r--wiki/cool-urls-can-change.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/wiki/cool-urls-can-change.md b/wiki/cool-urls-can-change.md
index 2979b42..54795f9 100644
--- a/wiki/cool-urls-can-change.md
+++ b/wiki/cool-urls-can-change.md
@@ -19,10 +19,11 @@ The web is not, much, like print media. Something published may be amended;
you don't even have to publish errata or a correction, since you can correct
the original mistake "seamlessly". This has its good and its
[bad](http://en.wikipedia.org/wiki/Memory_hole) parts, but with judicious use
-and a public history, amendment is more of a win than a loss. However, this
-plays havoc with the idea of a "publication" date, even for data that takes
-the form of an article: is the publication date the date it was first made
-public, the date of its most recent edit, or some other date?
+and [a public history](https://github.com/ojacobson/grimoiredotca), amendment
+is more of a win than a loss. However, this plays havoc with the idea of a
+"publication" date, even for data that takes the form of an article: is the
+publication date the date it was first made public, the date of its most
+recent edit, or some other date?
Because the name - the URL - of an article was set when I first published it,
the date in the name had to be its initial publication date. _This has