You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd love there to be an explanation of how CVFS works in detail, not the high level overview that README.md gives. Either in a dedicated file or a README.md for each project.
I am planning to publish a detailed paper very soon with the history of our design choices and how the current solution works. Coming very soon!
Reacted by Leonardo Carreiro, adyzng, Magnus Österlund, 染青42 and Waldir Pimenta
Reacted by Marc Brooks, Linglei Gong, Deepak Kumar, Sergei Voitovich, Shmueli Englard, Jan Melcher, Dan Smith, therealkenc, lizz, Karambir Singh Nain and 8 more
Johannes Löthberg (@kyrias) : hydrate/dehydrate objects etc I thought was a commonly known thing in the programming world ... Was for me, and made complete sense in GVFS's context because you know its all "virtualized" until touched
Update on this - a single white paper has turned into a project to write a series of articles. The first few of those are written and going through are publishing pipeline. Two of those articles are "GVFS Design History" and "GVFS Internals". So it's taking a little longer than I had initially planned, but it's on its way!
Reacted by Dan Smith, Vladimir Belozyorov, su21, Rafael Rivera, Magnus Österlund and Waldir Pimenta
The first few articles in our Git at Scale article series are now available: https://www.visualstudio.com/learn/git-at-scale/. This first batch includes an article on GVFS design history, and another is coming soon about the current inner workings of GVFS.
Reacted by Yue Lin Ho, Leonardo Carreiro and Kai Dorschner
Activity
kyrias commentedon Feb 3, 2017
Would also be useful with a small dictionary explaining some uncommonly used terms, and preferably how they came about, like hydrate.
sanoursa commentedon Feb 3, 2017
I am planning to publish a detailed paper very soon with the history of our design choices and how the current solution works. Coming very soon!
moderndev commentedon Feb 3, 2017
Johannes Löthberg (@kyrias) : hydrate/dehydrate objects etc I thought was a commonly known thing in the programming world ... Was for me, and made complete sense in GVFS's context because you know its all "virtualized" until touched
[-]How GVSF works[/-][+]How GVFS works[/+]sanoursa commentedon Mar 6, 2017
Update on this - a single white paper has turned into a project to write a series of articles. The first few of those are written and going through are publishing pipeline. Two of those articles are "GVFS Design History" and "GVFS Internals". So it's taking a little longer than I had initially planned, but it's on its way!
sanoursa commentedon May 24, 2017
The first few articles in our Git at Scale article series are now available: https://www.visualstudio.com/learn/git-at-scale/. This first batch includes an article on GVFS design history, and another is coming soon about the current inner workings of GVFS.
billziss-gh commentedon May 24, 2017
Saeed Noursalehi (@sanoursa) this is a great write up with genuinely useful information. Thank you for making it public.
steveknoblock commentedon Jun 30, 2017
Thanks for the article. I look forward to learning how you virtualized the access to the filesystem.
sanoursa commentedon Feb 21, 2018
Just published another article with much more information about how GVFS actually works: https://www.visualstudio.com/learn/gvfs-architecture/
sanoursa commentedon Jun 11, 2018
More articles will be coming out over time, but closing this issue out for now since the basics are covered. Please do post questions if you have any!
Merge pull request #2 from chrisd8088/linux-mirror-provider
Merge pull request #2 from derrickstolee/dstolee/case-rename-fixes