New answers tagged

0

Honestly the problem has been solved by not solving it. git is popular because of how well it makes working on the same repository easy, not by throwing locks on everything, which is in essence what you are asking for. It should be relatively seamless to work on the same file and merge changes back in. If not, use separate branches. And if the problem is ...


1

What about some thing like a daemon that Connected to everyone's box Frequently (every second? minute?) checked either which files are changed (a la git status) OR which files were currently open (sounds trickier, since that might be IDE dependent, and also not a fair question - I can look at a file without intending to change it) Conglomerates results ...



Top 50 recent answers are included