> project they are working on. Then they use TortoiseSVN to (mostly) commit > changes to their documents, sometimes to fetch older versions. Many of the > users are now making almost daily commits, not just just when making > official releases of their documents.
Thank you for sharing this. So the add/diff/branch/merge/pull SCM functionality is mostly under-utilized or even remains unused. Basically, the commit is used as an alternative Save. This is somewhat similar to how updates are handled in wiki/wordpress etc., where one just tracks the saves, without even comment attribution, just a timestamp. For such a use-case it'd be more user-friendly if there would be some kind of hook into the Save/Save As action (and perhaps Open) to allow more transparent VCS interactions. Not sure what's the best way to implement this, as it would be tied to the application which handles the edits. A plugin?? Or may be some watch service that polls for changes and picks up a new version and does the commit... Just thinking about finding a way to organically integrate VCS into ordinary user's workflow. BTW, back in the days of OpenVMS, file versioning was supported by OS itself, not sure if it has seen a huge demand, other than a need to do 'purge' to clean up the directories. But in my experience it was mostly an "Undo" feature, still the versioning was fairly transparent to the ordinary user. VCS should be able to handle this much better if it could be as much transparent to the user. _______________________________________________ fossil-users mailing list firstname.lastname@example.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users