Originally posted by boxie
View Post
Announcement
Collapse
No announcement yet.
Microsoft Announces Git Virtual File-System (GVFS)
Collapse
X
-
Originally posted by boxie View Post
not so, you don't *need* to have every single revision ever, and I can definitely understand the need for it.
Can't really see the point for normal projects however... Typically you need the vast majority of the files in the repo to do anything useful like build it or run the tests. Maybe with the linux kernel it would allow you to avoid other architectures but meh.
- Likes 2
Comment
-
Originally posted by zeehio View Post
What would be the advantage compared to this?Code:git clone --depth 1 path/to/repo.git
To my knowledge, there are 2 kinds of size issues:
1) The history is too big. In that case, why not just clone with --depth 1 as you mentioned?
2) When checked out, it takes up too much space. In that case, there are 2 sub-cases:
a) you need all of the checked-out files to build the project. In that case, there's no solution. MS' solution also doesn't help here.
b) you only need a few of the checked out files to build the project. In that case, split the project into smaller projects, and only clone the ones you need.
- Likes 6
Comment
-
Originally posted by ImNtReal View PostThe name might get a bit confusing: https://en.wikipedia.org/wiki/GVfs
- Likes 1
Comment
-
Originally posted by VanCoding View Post
b) you only need a few of the checked out files to build the project. In that case, split the project into smaller projects, and only clone the ones you need.
- Likes 1
Comment
-
You all do realize that besides the faster clone, with this you actually have a FULL CLONE, different than --depth 1, which would require manual pulling of data from remotes for every action that needs extra files. GVFS automates this task, enabling us to have a --depth 1-like fast clone, without sacrificing the accessibility of a full repo.
- Likes 4
Comment
-
Comment
Comment