<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 9, 2010, at 2:05 AM, Daniel Gackle wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I just pushed a patch (authored by Scott) to add .gitignore to the PS project so that fasls can be ignored. This is because, if you're using git submodules with PS, git thinks the library has changed every time you recompile it, unless you explicitly tell it to ignore fasls.<div>
<br></div><div>Git submodules aren't particularly simple, but we use them for one huge benefit: it lets git track which version of PS goes with which version of our code. So if we need to restore our system of a month ago, and there have been a bunch of patches to PS in the last month, git will check out the old version of PS that's contemporary with the old version of our stuff. This solves the huge headache of trying to run an old version of your code against newer versions of its libraries, which works until it doesn't and then is hard to track down.</div>
<div><br></div><div>I'd be interested if anyone has a better solution to this problem, because I'm not fond of git submodules, but am willing to live with them to get the above.</div></blockquote><div><br></div><div><br></div><div>A few alternatives:</div><div><br></div><div>1. Braid. This adds the files to the project. Can be bloat-y. I've used it in the past. For the most part, it works well. I've run into some really, really annoying conflicts with it's .braids file.</div><div>2. giternal (<a href="http://github.com/patmaddox/giternal">http://github.com/patmaddox/giternal</a>). I haven't tried it yet.</div><div><br></div><div>Regards,</div><div><br></div><div>(a different) Scott</div><meta charset="utf-8"></div><br></body></html>