Think about integrating version control

[DeflatedPickle]

It could be helpful in some cases to have backups of some files as they change. The best solution seems to be version control, with the ability to see each file's history

[nm17]

Built in small git client would be the best solution.

[DeflatedPickle]

Git is what I was thinking, as that's all I've used. But it's how it should be presented to the user that I'm conflicted with

Some users might want control of when things are comitted, some might want branching, some might want rebasing. Some might want it all automated

I want users to at least be able to;

• See the history for a file
• Clear the history
• Revert a file to a previous version

Which I have GUI in mind to do

I also want the Git stuff to be a plugin. Which means I now need events for when files should be commited, and the structure of that needs thought