> repos of unusual size
Sounds like they've almost solved the secrets of the fire swamp!
Announcing GVFS: Git Virtual File System
31–40 of 287 posts
Re: Announcing GVFS: Git Virtual File System
#32The article doesn't directly say it, but are they migrating the Windows source code repository to git? That seems like a big deal. I seem to recall that Microsoft has previously used a custom Perforce "fork" for their larger code bases (Windows, Server, Office, etc.).
Yes, Windows is migrating to Git.
Re: Announcing GVFS: Git Virtual File System
#33I think they could have picked a name that doesn't conflict with GNOME Virtual File System (GVfs).
When they picked the "Windows" product name, they could have picked a name that didn't conflict with the use of windows. Picking on an obscure file system doesn't even register in comparison.
X Windows
NeWS - https://en.m.wikipedia.org/wiki/NeWS
Remember the mess on usenet?
comp.windows.x.motif
comp.windows.new - not news about Microsoft Windows
Re: Announcing GVFS: Git Virtual File System
#34It's disappointing that all the comments are so negative. This is a great idea and solves a real problem for a lot of use cases. I remembering years ago Facebook says it had this problem. A lot of the comments were centered around that you could change your codebase to for what git can do. I'm glad there's another option now.
It's because the 'problem' it solves is a corner case that's rarely encountered. I love their absurd examples of repos that take 12 hours to download. How many people have that problem, really?
All they did is create a caching layer.
Re: Announcing GVFS: Git Virtual File System
#35It's disappointing that all the comments are so negative. This is a great idea and solves a real problem for a lot of use cases. I remembering years ago Facebook says it had this problem. A lot of the comments were centered around that you could change your codebase to for what git can do. I'm glad there's another option now.
Yes they did. They choose to scale out Mecurial to solve their problem. Wonder if they still use Mercurial?
https://code.facebook.com/posts/218678814984400/scaling-merc...
Re: Announcing GVFS: Git Virtual File System
#36Does this article imply that Microsoft itself is also moving towards Git? Instead of e.g. using their own product like TFS?
TFS has first-class support for Git repositories (in addition to the classic TFSVC repositories). So yes, they're moving more and more to Git. But no, they're not abandoning TFS. Interestingly, however, most of their "open source" efforts (.NET, C#, and related) are all on GitHub rather than their own hosted offerings: CodePlex (which is basically dead) or "Visual Studio Team Services".
Not sure why Visual Studio Team Services is in scare quotes -- that's the product's name. And it's not an open source hosting service, which handily explains why Microsoft's open source isn't hosted there.
Disclosure: I'm a PM on VSTS/TFS, and I own part of version control.
Re: Announcing GVFS: Git Virtual File System
#37Assuming that the repo was this big in the beginning, I wonder why the ever migrated to git (I'm assuming they did, because they can tell how long it takes to checkout). At least when somebody "tries" do the migration, wouldn't they realize that maybe git is not the right tool for them? Or did they actually migrate and then work with "git status" that take 10 minutes for some time until they realize they may need to change something?
Also, it would have been interesting if the article mentioned whether they tried other approaches taken by facebook (mercurial afaik) or google.
Re: Announcing GVFS: Git Virtual File System
#38Earlier quoted context omitted.
Hmmm.. Both Facebook and Google have giant monolithic repositories and use trunk based development and i'm guessing you wouldn't say they do it wrong. So not surprised Windows does
This is the Internet. There's always someone who'll say " they're doing it wrong! "
While never offering a suggested improvement.
Re: Announcing GVFS: Git Virtual File System
#39I think they could have picked a name that doesn't conflict with GNOME Virtual File System (GVfs).
They used to choose very bad names like .NET or COM [1] (this predates Internet) makes searching information very tricky. MSDN doesn't help. [1] https://en.wikipedia.org/wiki/Component_Object_Model
A few years ago I had to do some interfacing between python and some modelling software. I went through a COM interface, and it was a bloody nightmare to find docs.
I later found out I could have looked for "ActiveX" and found similar results.
Re: Announcing GVFS: Git Virtual File System
#40This is pretty big news. I know that when I was at Adobe, the only reason that Perforce was used for things like Acrobat, is because it was simply the only source control solution that could handle the size of the repo. Smaller projects were starting to use Git, but the big projects all stuck with Perforce.