31–40 of 50 posts
Earlier quoted context omitted.
http://xkcd.com/1205/ If you pull 10 times a day (conservative for me) then you’ll save ~5 hours over a year.
But couldn't it very well take more than 5 hours to set this up?
Too bad it doesn't work on Cygwin. (I share my ssh config between Linux and Windows.) Too bad ssh doesn't have conditional configuration. (Yes, I know I could script this, but it's a little more pain than I want for this gain.)
Earlier quoted context omitted.
http://xkcd.com/1205/ If you pull 10 times a day (conservative for me) then you’ll save ~5 hours over a year.
But couldn't it very well take more than 5 hours to set this up?
Earlier quoted context omitted.
Does this buy you that much over a SSD?
swap on ssd is (pseudo and slower) increased ram on big needs. Example: $5 digital ocean droplet (comes without swap, but it's over SSD, so you can create a swap file, and is less painful than mechanical swap).
Surely if they do, they won't for too long if lots of people start doing this.
Earlier quoted context omitted.
> This makes using ControlMaster workable. Best part of reading this article. I had turned off connection sharing because of this. So what, in more details, are the downsides to ControlPersist?
One that I frequently run into is that if you use SSH tunneling (like -L), you have to specify it the first time you ssh to that machine (i.e. when the ControlMaster is connected) and can't change it later. Using -L on later ssh's to the same machine silently fail, which can be infuriating if you don't realise it's happening. The best you can do at that point is to kill the ControlMaster ssh (disconnecting you across…
Earlier quoted context omitted.
But couldn't it very well take more than 5 hours to set this up?
It took me less than five seconds to make the SSH changes and less than five minutes to set up the intermediate server. Now I also have a cache for when GitHub goes down (all the time.)
Isn't the `.git` a cache for when github goes down? Git keeps all of your history inside your repository; you don't need network access to do anything.
What can be done to prevent the "Connection to github.com closed by remote host" error that comes a few minutes after a push/pull with the Control settings enabled? Since I'm normally in vim by then, it ruins the layout.
Earlier quoted context omitted.
It took me less than five seconds to make the SSH changes and less than five minutes to set up the intermediate server. Now I also have a cache for when GitHub goes down (all the time.)
> Now I also have a cache for when GitHub goes down (all the time.) Isn't the `.git` a cache for when github goes down? Git keeps all of your history inside your repository; you don't need network access to do anything.