You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Very interesting ideas you've put here. I was thinking about just opening a pull request, but hopefully you welcome some comments this way, too (if you like a concrete PR more, let me know).
on the examples for LightGitBags (an idea I find intriguing) and Using the history: You could make a more useful commit message to show how powerful the history could be, e.g. "Modify data/1930-02-10-05.tif: the previous scan of the original showed compression artifacts in the upper right corner and was re-done".
I know it might be a mood point as there are differentopinions, but I strongly suggest to use present tense / imperative mood in git commit messages to "Treat the git log not a history of your actions, but a sequence descriptions of what all the commits do. ". Some reading, if you are interested: http://chris.beams.io/posts/git-commit/
IMHO telling a more of a story with the commit messages could help to convince readers.
What's your take on git-lfs? I think your idea would profit from integrating it.
git-annex might be worth mentioning as an alternative (this blog entry has a nice comparison, and lists more alternative but stale projects)
The text was updated successfully, but these errors were encountered:
Hi! Very interesting ideas you've put here. I was thinking about just opening a pull request, but hopefully you welcome some comments this way, too (if you like a concrete PR more, let me know).
The text was updated successfully, but these errors were encountered: