Git makes a lot more sense thought of as a content-addressable filesystem the designer of which had "absolutely no interest in creating a traditional SCM system." (Not intended as snark! It's the real literal answer to a lot of my "why the heck is this like this?" questions.)
-
This Tweet is unavailable.
-
It's an interface issue, I think. It's not just that the internals are filesystem internals; it's that in a lot of ways the interface is a filesystem interface, not a version control one. So, translating between a VCS job I want to do and a Git command is often nontrivial. [3/N]
My instincts as a user of good software is to assume that if I'm doing too much of that kind of translation, I'm using the software wrong or misunderstanding it. Not so with Git, perhaps. [4/4]
-
-
This Tweet is unavailable.
-
I think git status works in part by looking at recently modified files, hashing their contents, and comparing them to object IDs (that are hashes). Maybe some of this is wrong? I'm not a git expert. But I think that's a pretty snazzy idea.
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.