Versioning with git

[sschober]

Idea

Each file you open is versioned using a (hidden) git repository in the users home directory (maybe ~/.qarkdown/<repo>).

Issues

Repo Uniqueness

How do we find a sensible repo-name? A hash on the path might be a good idea. But then you'd loose all history when you rename or move the file (because qarkdown would not be able to locate the hidden repo).

This problem is broader: The version history is then tied to the availability of the hidden repo. This means on different machines there will be different histories. This leads to the issue what qarkdown should do if there are edits outside of qarkdown.

Version Granularity

When is a new version created? Each key stroke might be too much, on every save might be not often enough.

User Interface

How is the navigation along the versions handled UI-wise? Should branching be supported? (Imagine a user reverts back to an earlier version of his file and then makes some further edits.)

Links

• libgit2 seems like a good starting point; there is also a Qt wrapper from the KDE project, but that seems not so terribly active (last commit 8 month ago)

[crdx]

I like this idea.