On Wed, May 27, 2015 at 10:05 AM, Dirk Hohndel <d...@hohndel.org> wrote: > > Even given that libgit2 uses libssh2 it should still be possible to craft > a way to communicate with a server and keep a repository synced with that > server...
I actually spent some time trying to figure it all out, and literally gave up. My .ssh/config file has things like host dives HostName git.subsurface-divelog.org Port 2222 User git IdentityFile ,,, to specify the port-name and user name etc. Even *that* kind of trivial thing seems to be a major pain with libgit2. But the "IdentifyFile" thing is just too painful for words. Hardcoding it to just work with github.com and user "git", and hard-coding a path to an identity-file (and require that it has no password) might be somewhat reasonable. There is rudimentary support for things like identityfiles per se in libgit2, it's just that there is no integration with normal ssh configurability. That said, even then I don't really know how to specify how to try to connect and give up quickly if not connected (or if just really slow connection). That doesn't seem to be a libgit2 usage model. Linus _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface