aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortschwinge <tschwinge@web>2009-03-19 17:31:53 -0400
committerJoey Hess <joey@kitenet.net>2009-03-19 17:31:53 -0400
commit3534d524ab9108fde2a7be1864e6adb8550aa4f1 (patch)
tree71a29e6eadc74aa29ecae47dc4c2aaff2e3064ca
parentdeca107db5e8a0537c37cacce63cb1672155abaa (diff)
downloadikiwiki-3534d524ab9108fde2a7be1864e6adb8550aa4f1.tar
ikiwiki-3534d524ab9108fde2a7be1864e6adb8550aa4f1.tar.gz
ikiwiki's notion of time
-rw-r--r--doc/forum/ikiwiki__39__s_notion_of_time.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/forum/ikiwiki__39__s_notion_of_time.mdwn b/doc/forum/ikiwiki__39__s_notion_of_time.mdwn
new file mode 100644
index 000000000..f52989026
--- /dev/null
+++ b/doc/forum/ikiwiki__39__s_notion_of_time.mdwn
@@ -0,0 +1,24 @@
+I'm having some difficulties with ikiwiki's notion of time.
+
+For (regular) pages, the *last edited* date is the one where the file
+was indeed last modified according to the file system information.
+The *created* date (commented out in the HTML) is, at least for
+`--getctime` operation, the date, where the file was last registered
+as changed with the VCS.
+
+Now, at least with git, the thing is that when you're checking out files,
+they'll get the checkout-time's current time stamp.
+
+What I strive for is the following: *created* be the date when the file
+(under its current name) was *first* registered with the VCS (which is
+more logical in my opinion), and *last edited* be the date the file was
+last registered as changed with the VCS, which is the current
+`--getctime` *created* date.
+
+This means that I can build the HTML files from different checkouts of the
+VCS and they won't differ in the time stamps they contain in the HTML.
+
+What is the rationale for ikiwiki's current behavior with respect to these
+time stamps?
+
+--[[tschwinge]]