summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-03-19 16:55:22 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-03-19 16:55:22 -0400
commitc1affb549de74ec13d8933732fed8a9859bf50b6 (patch)
tree83b355b03abe870270d1560926dca6fbf2174c18
parenta59bd278d765b63163aba829ee838d269308f987 (diff)
devblog
-rw-r--r--doc/devblog/day_137-138__bug_triage_and_too_much_windows.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/devblog/day_137-138__bug_triage_and_too_much_windows.mdwn b/doc/devblog/day_137-138__bug_triage_and_too_much_windows.mdwn
new file mode 100644
index 000000000..feff2ba8a
--- /dev/null
+++ b/doc/devblog/day_137-138__bug_triage_and_too_much_windows.mdwn
@@ -0,0 +1,15 @@
+Yesterday, worked on cleaning up the todo list. Fixed Windows slash problem
+with rsync remotes. Today, more Windows work; it turns out to have been
+quite buggy in its handling of non-ascii characters in filenames. Encoding
+stuff is never easy for me, but I eventually managed to find a way to fix
+that, although I think there are other filename encoding problems lurking
+in git-annex on Windows still to be dealt with.
+
+Implemented an interesting metadata feature yesterday. It turns out that
+metadata can have metadata. Particularly, it can be useful to know when a
+field was last set. That was already beeing tracked, internally (to make
+union merging work), so I was able to quite cheaply expose it as
+"$field-lastchanged" metadata that can be used like any other metadata.
+
+I've been thinking about how to implement [[required_content]] expressions,
+and think I have a reasonably good handle on it.