Git is awesome.
But it's terminology is really confusing.
But yeah some layer of abstraction would be handy.
I always think of introducing it to my wife when she looses a document or something but god damn the terminology.
But it's terminology is really confusing.
But yeah some layer of abstraction would be handy.
I always think of introducing it to my wife when she looses a document or something but god damn the terminology.
The lack of continuous versioning is a problem for most document like workflows.
So why do you expect the git hash to encode the timeline?
Git encodes the timeline in the parent/child relationship of commits (and/or the date stamps). Trying to look for the timeline information in the hashes is going to be futile, that's not where it's supposed to be found.
For documents that get send back and forth via email, amongst more than 2 participants, git's DAG is actually a better representation than a linear timeline.
(But yes, if you don't like that, you can set up git to reject commits with more than one parent to enforce a linear history.)
You get 30 days of history for every file in Dropbox (120 days for Business users). Earlier you could pay a bit extra to get a full year of history -- but that feature, called Extended Version History, is no longer available.
OneDrive unfortunately offers only 30 days, I believe Google Drive is similar.