4 ms·

But couldn't it very well take more than 5 hours to set this up?

• DougWebb 13y ago
  More like 5 minutes to set it up.
• Cthulhu_ 13y ago
  It is when you need to dig into the documentation to figure all of this out, but if you now google 'speed up git pull', you'll find this article, repeat the commands, ?????, profit! five minutes.
• nilved 13y ago
  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.)
  • gcr 13y ago
    > 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.
    • nilved 13y ago
      Sort of. I've automated synchronizing it with the GitHub repo, so my local repo may be behind the cached repo. I'm also protected if a repository is deleted/moved/DMCAed.
      • marblar 13y ago
        What benefits does this provide that a cron job running `git fetch` doesn't?
        • nilved 13y ago
          Redundancy, public access and not having hundreds of unused repositories on my computer. I'm not trying to sell anyone on the idea, it just works for me and I like it so whatever.
• eru 13y ago
  Doesn't matter too much. A short wait can throw you out of focus, and it's the time you spend getting back into focus that's important.