Easy question right? Just bare with me here..
I usually use Git to work with files on my local machine. I like this method because I can later check the files out on the shared drive for other non-git users to use. It is great because I can delete files (clean up) in my local directory and that cleans up remotely. I can leave all the extra files in the remote directory alone. This behaviour is why I do not simply
The only issue I'm having is in dealing with open files. Git stops the
reset when I encounter I locked file I need to change. Is this really a show-stopper? I may need to get a files out very quick and find it counter-productive to hunt down an unrelated open file blocking the process.
Can you help improve this process?
BTW: It is good enough to only update a file if the timestamp has changed. But I only want to update files that changed so that the incremental backups are not adversely effected.
Apparently this is uncommon so I'm not promoting it. The benefits are good for me though. This gives me fast local access to local files independent of network failure and basically seamless publishing to the backup drive. I just need to check-in often and push to make sure changes are backed up. It plays nice with other non-git files and users on the shared drive. Rsync falls short only because of the 'clean-up.' I can't
--delete clean up without removing other users files. It may sound minor to clean up manually, but it is really a deal killer as clean up is error prone and requires testing.