Integrity Integrity

17:47  Hi, anyone here building branches other than master with Integrity?  I ask because it seems that cloning a repository 'git clone -ns src dst' (as Integrity does to setup a build tree from it's 
                   cache repo) results in loss of branch info.  In the course of some experiments I believe it's git clone's 'shared' option (-s) that's causing this behavior.  Thanks!
17:50  doublefree, that's probably a bug
17:50  the cacching system isn't complete yet. I think i'll ditch it untill it is properly implemented
17:51  doublefree, can you tru without the -s switch?
17:51  sr:  I like the approach of using shared repositories to save disk space per build, I am going to try removing the -s option in Bob's git handler today.
17:51  cool
18:32  sr:  I spoke too soon, it looks like the -s option is not the issue.  it seems that a second degree clone loses branch info... I'm still a bit of a git noob, so perhaps this is expected 
                   behavior.
18:43  could you please try to reproduce this outside of integrity?
18:44  if that works then there is a bug bob
18:45  i'll remove the cache until that is more tested and/or fixed
18:58  here's how I was reproducing this outside integrity:  http://gist.github.com/152132
19:03  doublefree, why --bare?
19:04  we use bare repositories so that we can push to them without problems related to working copy getting out of sync
19:05  behavior is same if cloning off the original (non bare) repository
19:06  huum, doing "git checkout remotes/origin/#{branch}" in bob might fix this
19:08  doublefree, like this: http://gist.github.com/7d3b97091cb21985fe3e
19:14  sr, no luck:  'error: pathspec 'remotes/origin/trim_test' did not match any file(s) known to git.'
19:23  doublefree, http://gist.github.com/8ad4c075747ebd30a908
19:23  that seems to work, so idk
19:24  maybe without the -n switch
19:24  I finish up something then I'll look at it a bit more deeply
19:29  sr, if you clone bar as if it was the cache repo the gonzo branch is still not there in bar's clone... I'll stick with master for now, thanks.
23:00  sr, I hacked together a possible solution to my branch issue that seems to be working well so far, here's the diff:  http://gist.github.com/152264