undefined | Better HN

0 pointschungy3y ago0 comments

Is it really that confusing for Git? I had basically that entire manpage memorized early on (even before the manpage existed....)

0 comments

4 comments · 1 top-level

masklinn3y ago· 3 in thread

> Is it really that confusing for Git?

Complete shit is what it is.

It's awkward, messy, inconsistent, and hard to compose.

IshKebab3y ago

The CLI and nomenclature for the staging area (what should be called "draft commit") is awful, but the actual concept is very easy to understand.

I seriously doubt anyone who uses a sane interface to Git (e.g. a GUI) has any trouble with clicking + to add changes to the draft commit before committing it.

Most GUI tools let you automatically add all changes before committing anyway so you don't have to know anything about it if you don't want to.

They just needed to name things better (what is a "soft reset" again?).

jcranmer3y ago

The main problem I have with the staging area is that it amounts to being something that's like a commit except for, you know, not actually being a commit, and therefore things that normally work on commits don't necessarily work on the staging area.

A better fix would be to make the staging area an actual commit, and then reframe everything as easy ways to edit the latest commit. (This meshes well with adding features like Mercurial's phases or changeset evolution that make commit editing somewhat safer).

1 more reply

masklinn3y ago

What are you talking about? My comment is about gitrevisions(7).

j / k navigate · click thread line to collapse