Hacker News new | past | comments | ask | show | jobs | submit login

> It's a shame how poor the command-line usability of the git client is.

In comparison to an average CLI program's usability, I think git's got a very good one. It's not perfect, but I think saying it's "poor" is really exaggerating the problems.

In particular, I love how well it does subcommands. You can even add a script `git-foobar` in your $PATH and use it as `git foobar`. It even works with git options automatically like `git -C $repo_dir foobar`.

> It's really hard to explain to new users why you need to run `git checkout HEAD * ` instead of `git reset` as you'd expect

Why would you ever do `git checkout HEAD * ` instead of `git reset --hard`? The only difference is that your checkout command will still leave the changes you've done to hidden files, and I can't think that's ever any good.

> why `git branch [branchname]` just switches to a branch whereas `git checkout -b [branchname]` actually creates it

If you think those behaviors should be switched, good, because they are.

EDIT: How did you manage to add the asterisk to the checkout command in your post so that it's not interpreted as italics without adding a space after it?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: