I'm using Live Mesh to sync between my home and work computer mostly.
Being a software developer, I like to share my local "Git" repositories
between my home and work machine. (Git is a distributed version control
sytem.) The projects I work on are proprietary software, so I cannot
choose Github or any other public Git hosting to share code between the
two machines. The reason why I have to do the sync on top of Git in the
first place is that we're using Subversion as our authorative SCM, but
I also don't want to miss the features of Git (especially local
branches).
Anyways, after that long introduction, here's my Live Mesh question:
During the Tech Preview days of Live Mesh Git sync worked perfectly and
without a glitch. Since I installed the beta, I keep getting changed
files over night. Say I finish my work in the evening and keep the box
running overnight with a "clean" Git repository. When I come back to my
machine the next moring, there are a couple of files changed. During
that nighttime I didn't use that synced folder, nor was my other LM box
turned on.
The question that bugs me is if there were some changes introduced to
the beta that cause these updated files, and if you could test Live
Mesh with Git repositories. They might be a bit special because they're
accesses through Unix-style tools (via Cygwin).
Can you contrast the changes found during the overnight activity with what is found in your cloud storage on your Live Desktop? What I am wondering is if you are pulling versions down from the cloud hosted folder and if those are being placed in your local folder.
Thanks,
TimProgram Manager | Live Mesh
Proposed as answer byBen [Live Mesh]Monday, November 10, 2008 6:14 PM
Marked as answer byBen [Live Mesh]Tuesday, December 9, 2008 9:20 PM