Thinking as if we had to implement locks some day... I just thought that we could have locks working not on file-paths-in-branch, but on artifacts. That would expand well to multiple branches.
Then, if anyone gets the lock, and commits a new version, it could get locked automatically too, expanding the list of artifacts needing lock. Those artifacts that 'require lock' for edition could be checked out read-only. The list of locked artifacts could expand similar to the shun list, that can be told to be updated on autosync. And the list of lock owners too. Keeping the default remote as the source of locks. And apart, not requiring a locks implementation, there could be a fossil default-off option to simply check out binary files readonly (fossil seems to know what file is binary and what not). That would put a step before binary-file editions, inviting to team communication. If anyone think locks could help in their use of fossil, that chould give an opinion on this. I work either in a small team or alone, so I'm not very representative on this. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
