3 ms·
+1 for the outreach. They definitely lost control of the announcement, since it got out yesterday. The nice thing about it is, everyone who keeps their Git re
by CaliforniaKarl 8y ago
+1 for the outreach. They definitely lost control of the announcement, since it got out yesterday.
The nice thing about it is, everyone who keeps their Git repo up-to-date (and who has the transfer.fsckobjects setting set to true) has a complete copy of the Git repo. And GitHub provides APIs to pull other stuff. I think the hardest thing to move would be sites on GitHub Pages.
So, since I can pull out relatively easily, I'm gonna give them the benefit of the doubt.
- cma 8y agoWhat's missing without transfer.fsckobjects ?
- bacongobbler 8y agohttps://git-scm.com/docs/git-config/1.7.9.3#git-config-fetchfsckObjects https://git-scm.com/docs/git-config/1.7.9.3#git-config-fetch... My interpretation is that transfer.fsckObjects just checks that all of the fetched objects are properly formed and contain no broken links. I cannot confirm whether or not this fetches any extra objects from the remote; this is the first time I've heard about this feature.