Tay Ray Chuan <rctay89@xxxxxxxxx> writes: > Hi, > > some time ago I noticed curl doesn't remember your credentials (apart > from those it can get from ~/.netrc), and very recently there was an > thread on repeated prompting for credentials while pushing to https. > > I've written a simple patch series, which allows git to play nice > without curl_multi. That is, git uses a single persistent connection > throughout. > > However, I'm at a loss at how to test for this. How does one count the > number of connections made during the lifespan of a program's > execution? So far, I've been relying on my firewall log (Comodo on > windows). Perhaps there a more operating system/software-agnostic > method to do this? You could set up a single-use tcp forwarder which will make any second connection fail. Using socat, for instance: $ socat tcp-listen:2222,bind=localhost tcp:my.server:22 & $ nc localhost 2222 SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 ^C $ nc localhost 2222 localhost [127.0.0.1] 2222 (?) : Connection refused -- David Kågedal -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
