3 ms·
For the avoidance of doubt, GitHub is not upstream of Git.
by jwilk 9y ago
For the avoidance of doubt, GitHub is not upstream of Git.
- tomxor 9y agoyeah this was really confusing in the article everywhere it mentions up-streaming it refers to "git" only then later mentions how GitHub is accepting it's modifications... so not entirely sure which it is. TL;DR pretty sure it's not touching git source at all. Looking though the GVFS readme: https://github.com/Microsoft/GVFS https://github.com/Microsoft/GVFS it appears that it actually wraps git, which would make sense because in that case they would have to explicitly add support to each git host and provide individual platform ports of GVFS (all of which would be unnecessary if it was actually upstreamed into git). So that's good... git is one of my favourite open source tools and I would really hate for M$ to start polluting it. I don't care if GVFS is a good idea or not I just don't trust the fuckers and they will always deserve that suspicion.
- hdhzy 9y agoNo, they needed to do some modifications to the git suite of tools. Generally git expects all objects to be on disk and Microsoft wanted to have sparse checkouts of files in a specific revision. Not really polluting but rather having some objects be fetched only on demand. Source: https://blogs.msdn.microsoft.com/devops/2017/02/03/announcing-gvfs-git-virtual-file-system/ https://blogs.msdn.microsoft.com/devops/2017/02/03/announcin... > In addition to the GVFS sources, we’ve also made some changes to Git to allow it to work well on a GVFS-backed repo, and those sources are available at https://github.com/Microsoft/git https://github.com/Microsoft/git. For the record as far as I understand GVFS the article is correctly using git vs Github.
- tomxor 9y agoThanks for the clarification, sparse object fetch seems like a small change in concept at least.