3 ms·

The question is not when do you do development offline? The question is when have you ever needed the ENTIRE history of the repository offline? Have you? Maybe

• falcolas 12y ago
  > Do you constantly need to? "Constantly" doesn't matter. If you ever need access to the entire history while offline and it's not there, you can't work. Disks and bandwidth are both relatively cheap, compared against the value of having access to the data.
• pm24601 12y ago
  Yes I do need the entire repo: 1) when a developer "accidentally" deleted the master repo. 2) when a developer accidentally damaged the master repo with a force push and it was easier to drop and restore the repo from my disk version. 3) when I am figuring out the overall contribution that each developer made. 4) when i am running a git bisect to figure out when a bug was introduced. 5) ... other cases. As another person said, its not that I always need the full repo its just that I need it on occasion and I don't know when I will need the full repo. And those times when I need the full repo, I may be flying overseas or at my mom's house ( and she doesn't have internet ). By the simple expedience of having the full repo with me, I don't have to worry about needing an older version of a file ... or anything.
• twic 12y ago
  I use blame quite a bit, along with the pickaxe in Git and revsets in Mercurial. Those involve querying over the history of the repository - potentially quite a large fraction of it. I'm glad to be able to do that locally, limited by the speed of my SSD rather than min(the latency of my broadband connection, my tiny slice of GitHub's disk bandwidth).