| 01:22.19 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 01:22.19 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 01:22.19 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 05:13.23 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 06:51.11 | *** join/#qi-hardware _whitelogger (~whitelogg@uruz.whitequark.org) |
| 06:51.11 | *** mode/#qi-hardware [+v _whitelogger] by ChanServ |
| 07:28.43 | *** join/#qi-hardware kyak (~kyak@95-27-243-21.broadband.corbina.ru) |
| 07:28.43 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 07:42.10 | *** join/#qi-hardware _whitelogger (~whitelogg@uruz.whitequark.org) |
| 07:42.10 | *** mode/#qi-hardware [+v _whitelogger] by ChanServ |
| 10:23.42 | *** join/#qi-hardware dandon (~dandon@185.16.53.101) |
| 11:43.26 | *** join/#qi-hardware erichvk__ (~esh@ppp118-210-219-39.lns20.adl6.internode.on.net) |
| 13:42.42 | *** join/#qi-hardware dandon (~dandon@185.16.53.101) |
| 17:25.22 | *** join/#qi-hardware pcercuei (~pcercuei@92.177.36.45) |
| 17:57.47 | *** join/#qi-hardware sb0 (~lekernel@210006059234.ctinets.com) |
| 18:19.35 | *** join/#qi-hardware sb0 (~lekernel@210006059234.ctinets.com) |
| 19:32.13 | *** join/#qi-hardware wildlander (~wildlande@unaffiliated/wildlander) |
| 21:45.42 | 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.48 | 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.13 | 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.52 | 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.27 | whitequark | wpwrak: have a toplevel repo |
| 21:50.31 | whitequark | is the usual solution |
| 21:50.32 | 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.20 | wpwrak | ah yes, that sounds nice. basically mixing both approaches |
| 23:10.32 | 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.34 | wpwrak | grrr... |