3 ms·
> What's the staging area? It's essentially a commit-in-progress Aha, that's where the typical view of VCSes shows through the cracks of our old habits: here c
by lloeki 10y ago
> What's the staging area? It's essentially a commit-in-progress
Aha, that's where the typical view of VCSes shows through the cracks of our old habits: here commit is not an object, it's an action. So there's no "commit-in-progress" because either you commit or you don't, and the operation is virtually atomic. The fact that object with badcafe sha1 records the history of that action and is called "commit badcafe" in the log is incidental, and we're being abusive when we're literally saying the commit is the object.
So when you say git commit --amend, it's really no different than git commit, because you're just telling it to do the very same thing, only with a git reset HEAD^ before that.
That said, I'll readily admit the UI is poor, mostly because it's grown, not designed.
- bryanlarsen 10y agoIn my view of git, commit is very definitely an object, the action is 'creating a commit object'. I don't think either of us is wrong, we just use different names, making communication very difficult. Which just underscores my original point. Names matter.