4 ms·
Hrm, so this isn't about making git 50x faster but fast network communication. > Establishing an SSH connection every time you perform a Git operation costs ma
by nkuttler 13y ago
Hrm, so this isn't about making git 50x faster but fast network communication.
> Establishing an SSH connection every time you perform a Git operation costs many round-trips
I don't really understand why the author is saying this. The whole point of git is to be distributed and not to push/pull at each commit.
That being said, he found something that speeds up his workflow tremendously, so congratulations.
- eru 13y agoOh, you might still want to share your commits with your coworkers, and for that you need to push and/or pull. (You could do that asynchronously, though.)
- dlitz 13y agoEven with a short timeout (say, 10 seconds), it could be useful for a maintainer who pulls from several other users' GitHub repositories. Instead of establishing a new SSH connection for each remote, a complete "git remote update" of multiple repositories could be done over a single connection.