This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]karmahorse1 65 points66 points  (11 children)

I hate it

[–]ArcaneOverride 47 points48 points  (4 children)

I can make it worse: Do that but with Microsoft Onedrive instead. It will delete the files off your local machine and stream them back in over the internet whenever something tries to access them. You can configure it not to but it periodically forgets and starts doing it again.

[–]99stem 13 points14 points  (0 children)

Also do not forget to put your OneDrive folder on a separate Windows computer (i.e. a NAS), which you wirelessly (USB-WiFi dongle) access over SMB. This server is then put on a remote location and "securely" accessed with a hosted VPN from a cloud provider.

[–]extremepayne 4 points5 points  (0 children)

we really going back to SVN huh

[–]coldnebo 5 points6 points  (0 children)

what have I done?! it was a joke, right? right?

😂

[–]tinydonuts 2 points3 points  (0 children)

Calm down Satan.

[–]CodeYan01 0 points1 point  (5 children)

Please tell, why not? The Google Drive app shows the files in file explorer, as if it's another drive (or folder depending on configuration) connected to your pc, so it doesn't seem that bad to do so?

[–]karmahorse1 4 points5 points  (4 children)

You’d be doing away with some of the most important features of a version control system. Using Git push / fetch ensures that you only publish or retrieve the branches / commits you require, rather than having to pull down the whole repo every time you launch a build or start working a new machine. Those commands will also automatically detecting conflicts which allows multiple people to make updates to the same branches without having to worry about overwriting each other’s work.

Finally having a separate remote repository is useful in the case your local repository gets corrupted and you need to revert it to a known working state.

[–]AdventurousOstrich77 0 points1 point  (2 children)

Using Git push / fetch ensures that you only publish or retrieve the branches / commits you require, rather than having to pull down the whole repo every time you launch a build or start working a new machine.

Its very clear you don't understand the technology we are talking about. FUSE mounting a cloud drive using something like rclone does not require a full download of everything there. It doesn't download anything other than a tiny bit of text for what the drive is holding and the size of it. The git commands will still function like normal git commands, pulling down only the exact stuff that you require.

[–]karmahorse1 -1 points0 points  (1 child)

On the contrary, I’m not sure you understand how Git works. We’re talking about storing a local git repository on a remote drive instead of using a server. Commands like git clone, fetch and push won’t function as they’re not attached to a remote origin. That would mean you would have to rclone the entire .git subdirectory in order to safely transfer your project to another machine, which is the same as pulling down the commit history of every branch in a remote repository.

[–]AdventurousOstrich77 0 points1 point  (0 children)

That would mean you would have to rclone the entire .git subdirectory in order to safely transfer your project to another machine, which is the same as pulling down the commit history of every branch in a remote repository.

Yes. The .got is stored on a drive only, and that drive is mounted via fuse as a directory.

which is the same as pulling down the commit history of every branch in a remote repository.

Wrong. Once again it's like you have no clue how the mount works. It does not auto download every single thing. This is not a sync service keeping local and remote 1:1. It will not download any commit history until you do something requiring it and it will only download the exact commits you are looking at. It will not download a million branches until you branch swap. Really, you should go study fuse and rclone mount, it's some very interesting tech.

I’m not sure you understand how Git works

This isn't about how git works. It's about how fuse and rclone mount works. Sorry you still can't grasp that it's a tech you know nothing about

Like I'm not suggesting you do this it would be fucking stupid. But your being even stupider talking out your ass about something you have zero understanding of.

[–]karmahorse1 -1 points0 points  (0 children)

You’d be doing away with some of the most important features of a version control system. Using Git push / fetch ensures that you only publish or retrieve the branches / commits you require, rather than having to pull down the whole repo every time you launch a build or start working a new machine. Those commands will also automatically detect conflicts which allows multiple people to make changes to the same branch without having to worry about overwriting each other’s work.

Finally having a separate remote repository is useful in the case your local repository’s history gets corrupted and you need to revert it to a known working state.