summaryrefslogtreecommitdiff
path: root/doc/forum
diff options
context:
space:
mode:
authorhttp://seanh.myopenid.com/ <http://seanh.myopenid.com/@web>2009-04-01 07:26:06 -0400
committerJoey Hess <joey@kitenet.net>2009-04-01 07:26:06 -0400
commit0d2769f4bae4e44e20c6cc5d9f9b3dec3d5effd2 (patch)
tree2837dc836f9c67ecd4c5c88c7f3b42f36f1955ed /doc/forum
parent33fa78a66f1248b7cec4cba21d125117dffa9c90 (diff)
Diffstat (limited to 'doc/forum')
-rw-r--r--doc/forum/How_does_ikiwiki_remember_times__63__.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn
new file mode 100644
index 000000000..c23f0b100
--- /dev/null
+++ b/doc/forum/How_does_ikiwiki_remember_times__63__.mdwn
@@ -0,0 +1,10 @@
+This is similar to the last post in this forum. I want to know exactly how ikiwiki remembers the times associated with pages, especially when using it for blogging, so I know whether I can trust it or not. From that last thread, I think what ikiwiki does is this:
+
+* The created time of a file is when that file was first committed into the versioning repository (in my case git)
+* The modified time of a file is what that file was last updated in the repository
+
+And with a blog, by default, the posts are ordered by creation time, although an option can order them by modified time.
+
+Okay. So this should mean that the times are safe if, for example, I delete my working copy and then clone another one from the bare git repository, or otherwise mess up the creation times and mtimes stored as file metadata on the filesystem.
+
+Do I have it right?