libgit2/rugged — pull request #62 by arthurschreiber (2012-06-02 13:01:24+00:00)
Title: Update to libgit2 0.17.0.

All tests expect the `"is able to connect to the remote"` pass, but I investigated that one and it seems to be caused by a bug in libgit2 itself.

Specifically, all transports never reset their `connected` attribute to 0 when they're closed. That's then causing `Rugged::Remote#connected?` to always return 1 after a connection has been established once.