Email or username:

Password:

Forgot your password?
Julia Evans

has anyone seen a really good analysis of the problems with git's command line UI? Would love to read it. for example:

* `git checkout` is dangerous and has too many different jobs
* for a tool that's supposed to make changes easy to undo, you actually need to learn a LOT of different ways go back to the previous state

(not looking for git tutorials, explanations of git’s underlying model, or explanations of why you think git's UI is actually good, just an analysis of the problems)

6 comments
Benjamin Pollack

@b0rk I don't, but I'd be *super* interested in seeing any actual methodical study of it. Even having worked in the DVCS space, I'm mostly aware of what I'd at best call shared communal anecdata, which is somewhat frustrating

groxx

@b0rk tbh I think a significant amount of it is their incredibly unique-term-infested manpages. Learning git via normal means is a ridiculously large investment before you get any benefit.

git-man-page-generator.lokalto

penguin42

@b0rk I dont find it too bad, but I do find it inconsistent; e.g. git tag and git branch both have -d for delete, but for git remote you have to do 'git remote remove' Similarly git branch -m to rename vs git remote rename. git push onto non-default branches also confuses the hell out of me.

joachim

@penguin42 @b0rk Yup, this - the different commands are inconsistent. And 'remote remove' is just asking for typos!

Go Up