
Identically with that information is not feasible. If it does, then having several machines configured (.git dir) and require that information in order to properly manage (Q) Does GIT store information on a host outside of the GIT repo Here are the questions I have that will help me understand if this is even technically possible (NOTE: I'm already experimenting with this approach). Everything I've read says you can't (or shouldn't do this). So now I'm wondering if this same approach can work using GIT. For me this is simple enough and has worked well.
#Subversion hosts update
When I return from a business meeting or trip, I commit my changes on my laptop and update run svn update on any one of the 5 VMs and the files are updated for all 5 VMs. I work from home so this is not frequent. I also do not have to commit files until I'm taking my laptop for a business meeting. In some cases, my svn repos are many years old and over 2 GIG having separate "SVN working areas" in each VM makes my VMs larger and complicates my VM Snapshots, and backups.

This approach lets me access the server's file share (\host1\share) from any host. I'm currently using Tortoise SVN 1.8.2, and subversion 1.8.3 (on ALL of the hosts). Laptop (access SVN working dir \\host1\share\svnproj1)īut also have a svn checkout at c:\svnproj1Īll of the OSs are Win7圆4 or Win8.1圆4. +vm5 (access SVN working dir \\host1\share\svnproj1) +vm4 (access SVN working dir \\host1\share\svnproj1) +vm3 (access SVN working dir \\host1\share\svnproj1) +vm2 (access SVN working dir \\host1\share\svnproj1) +vm1 (access SVN working dir \\host1\share\svnproj1, and svnproj2) I have several large disks on "host1" and have file shares that other hosts (in the local LAN) access. I have a couple beefy machines each running several VMs. To understand why I'm looking to do this consider my configuration (below). In short, I'm willing to live with some limitations (if necessary) to simplify the overall management of my personal projects. It's important to point out this this is a single user solution, and I'm the only person making changes so I'm not running SVN commits on multiple boxes at the same time. In subversion, I've used a shared SVN working directory on several hosts (despite people telling me it wouldn't work), and it's proven to work nicely for me. I'm transitioning my personal projects from using subversion (svn) to GIT.
