21:45 <wpwrak> btw, what's the collective wisdom regarding git repos with crossed dependencies ? i currently have them all under the same top-level directory, with relative symlinks picking stuff from the neighbours. e.g., file foo/src/Makefile may use ../../bar/whatever

21:46 <wpwrak> an alternative approach would be to use submodules instead. so foo/ may have a copy of "bar" as foo/bar/ or foo/src/bar/, and the Makefile would use ../bar/whatever or bar/whatever

21:48 <wpwrak> a minor twist here is that there are cases where something in repo A depends on something in repo B, but also something in B depends on something in A. so in the submodule scenario, each would have the other as submodule

21:48 <wpwrak> but i don't think there are cases where such an "external" dependency would go more than one step. i.e., no foo -> bar -> foo

21:50 <whitequark> wpwrak: have a toplevel repo

21:50 <whitequark> is the usual solution

21:50 <wpwrak> background: the anelok repo is getting messy, with circuit design, firmware, simulator, case design, build tools, the host gui, the web site, and documentation all lumped into one repo. so i'm thinking of breaking that down into multiple repos

21:51 <wpwrak> ah yes, that sounds nice. basically mixing both approaches

23:10 <wpwrak> how i love gtk. changing a label to a button i notice a little issue. issues stubbornly refuses to go away. finally i give up and google: http://stackoverflow.com/questions/26089342/python-gtk-3-table-buttons-should-not-expand/26092410#26092410

23:10 <wpwrak> grrr...