{"thread":{"id":"38491","subject":"symlinked files","startedAt":"2015-02-03T09:12:57Z","lastAt":"2015-02-03T09:12:57Z","messageCount":1,"participants":["Hans Kristian Otnes Berge"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"255569","messageId":"006001d03f91$a00d0500$e0270f00$@ifi.uio.no","threadId":"38491","inReplyTo":null,"subject":"symlinked files","fromName":"Hans Kristian Otnes Berge","fromEmail":"hansbe@ifi.uio.no","sentAt":"2015-02-03T09:12:57Z","receivedAt":"2015-02-03T09:12:57Z","isPatch":false,"sender":{"key":"hansbe@ifi.uio.no","avatar":null},"body":"Hi\n\nFirst of all thanks for a great piece of software!!\n\nI have a tiny complaint though, about git not allowing symlinked files (in\nan easy way).\n\nI would use this to keep track of the contents of a file that is also being\ndeveloped and shared across other projects, but later changes to it could\nbreak a few things in each project. Although I understand it makes for some\ncomplications, and it fails to meet basic KISS principles, it would be great\nto be able to override the default behavior for instance via the config or\nadd command or something in the info directory. I suppose there are lots of\nwork-arounds to this (just a bit more hassle), so no worries if you don't\nlike it.\n\nThanks!\n\nHans Kristian\n"}]}