+ [2014-10-05T20:43:56Z] milki o, that kind of reference
+ [2014-10-05T20:45:33Z] MikeClassic soerry I meant to reference an issue in another repo via commit msg, not another commit.. sorry
+ [2014-10-05T20:50:16Z] milki well, issues can still do that, so its all good
+ [2014-10-05T21:20:12Z] VxJasonxV MikeClassic: just link to it
+ [2014-10-05T21:20:26Z] VxJasonxV it will be shortened and referenced (provided you have push access to it, I think)

message no. 51353

Posted by lunaphyte in #github at 2014-10-05T03:26:15Z

i'm not sure if this is topical here, but i submitted a pull request, and i see a note: "the travis ci build failed": https://github.com/retspen/webvirtmgr/pull/449
+ [2014-10-06T00:54:42Z] xandros Hello, I have a repository on github and when I cloned it to my local machine and do a git branch in the command line, I only see master. Is there a way to pull/clone all branches from remote?
+ [2014-10-06T01:29:13Z] VxJasonxV git checkout -b branch-name
+ [2014-10-06T01:29:30Z] VxJasonxV you have all of the objects already, git just doesn't "set up" all the branches
+ [2014-10-06T01:29:32Z] VxJasonxV but all of the data is there
+ [2014-10-06T01:29:52Z] VxJasonxV since they're existing branches, you probably want to do: git checkout -b branch-name origin/branch-name