3 ms·

For me: 1. I do development offline all the freaking time. Basically I love the entire repo stored on my disk for the same reason I have a laptop instead of a

by pm24601 12y ago

For me: 1. I do development offline all the freaking time. Basically I love the entire repo stored on my disk for the same reason I have a laptop instead of a desktop - so I can code anywhere. 2. News flash there are plenty of places that do not get good internet connectivity. Or my phone maybe dead or dying. Or I just stopped caring about having the tethering option on my plan. (and didn't care enough to bypass the restriction ) 3. I don't use a lot of large images/video/etc in my development. Never have really, but then again I do a lot of server-side dev - very little Android coding. 4. Why do I care about a repo that is 1-2 gigabytes? I have a 4 terabyte disk. Overall, comment: problem for facebook and google - for most companies this is not a problem. And if your company is having this problem, it has the money and people to solve the problem ... like facebook and google are doing.

liveoneggs 12y ago
a 2GB git repo (without any binaries) probably has 4-5 million objects and will take a few GB of memory to clone and will otherwise be slow for status and other commands.
- pm24601 12y ago
  Sure. So what? Most repos I am dealing with are less than 200m. The problem of 1-2 gigabytes with millions of objects is simply not a big problem for most startups companies. Larger companies have the resources to solve this "problem".
  - liveoneggs 12y ago
    you asked.. > 4. Why do I care about a repo that is 1-2 gigabytes? I have a 4 terabyte disk.
- pm24601 12y ago
  also if this was the case I would make a second git repo a filtered version of the complete git repo. Sure it is a "hack" but it is an engineering solution to an engineering problem. Not all engineering solutions need to be idealized perfection.
philtar 12y ago
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. Do you constantly need to? Very very unlikely for the vast majority of people
- 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).

by pm24601 12y ago

liveoneggs 12y ago

a 2GB git repo (without any binaries) probably has 4-5 million objects and will take a few GB of memory to clone and will otherwise be slow for status and other commands.

pm24601 12y ago
Sure. So what? Most repos I am dealing with are less than 200m. The problem of 1-2 gigabytes with millions of objects is simply not a big problem for most startups companies. Larger companies have the resources to solve this "problem".
- liveoneggs 12y ago
  you asked.. > 4. Why do I care about a repo that is 1-2 gigabytes? I have a 4 terabyte disk.
pm24601 12y ago
also if this was the case I would make a second git repo a filtered version of the complete git repo. Sure it is a "hack" but it is an engineering solution to an engineering problem. Not all engineering solutions need to be idealized perfection.

philtar 12y ago

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. Do you constantly need to? Very very unlikely for the vast majority of people

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).