3 ms·

OT (or not) - Of 20 most popular Qs on SO, 7 now ask how to do trivial operations in git. http://data.stackexchange.com/stackoverflow/query/36656/most-upvoted

by avip 10y ago

OT (or not) - Of 20 most popular Qs on SO, 7 now ask how to do trivial operations in git. http://data.stackexchange.com/stackoverflow/query/36656/most-upvoted-answers http://data.stackexchange.com/stackoverflow/query/36656/most... Take it or live it, git has facts-based proven track record of ui wtfness.

qznc 10y ago
The two top questions are "How to modify existing, unpushed commits?" and "How to undo last commit(s) in Git?". That could be interpreted as evidence in favor of a staging area. People actually need to change committed things very often. On the other hand, on place 20 is "How to undo 'git add' before commit?", which displays a UI shortcoming with staging.
- avip 10y ago
  It suggests staging is confusing for newcomers (or maybe - for the mass in general).
  - crooked-v 10y ago
    A simple way to make it clearer: have 'git stage <file>' and 'git unstage <FILE>' commands, instead of the extraordinarily unintuitive 'git checkout -- <file>' for the latter.
jjnoakes 10y ago
I see beginner questions at the top of most tools on S.O. I don't think that implies anything about the UI of the tool. If anything, it probably implies something of the popularity. (I'm not arguing whether git's ui is good or bad, just that S.O. questions are probably a poor yardstick for deciding).
draw_down 10y ago
Not just that, the descriptions you find online of how it works simply don't prepare you for the reality of using it. It's a bunch of boxes and arrows when what you really want is what to do when things inevitably don't work how they are supposed to. I mean, everyone who has written a guide to rebasing must live on Mars. They show how your branch used to point to this box, but now it points to THIS box! And then what you really get when you actually try to use it is a bunch of conflicts between changes that affect files you haven't done anything to and a shit ton of confusion.

by avip 10y ago

qznc 10y ago

The two top questions are "How to modify existing, unpushed commits?" and "How to undo last commit(s) in Git?". That could be interpreted as evidence in favor of a staging area. People actually need to change committed things very often. On the other hand, on place 20 is "How to undo 'git add' before commit?", which displays a UI shortcoming with staging.

avip 10y ago
It suggests staging is confusing for newcomers (or maybe - for the mass in general).
- crooked-v 10y ago
  A simple way to make it clearer: have 'git stage <file>' and 'git unstage <FILE>' commands, instead of the extraordinarily unintuitive 'git checkout -- <file>' for the latter.

jjnoakes 10y ago

I see beginner questions at the top of most tools on S.O. I don't think that implies anything about the UI of the tool. If anything, it probably implies something of the popularity. (I'm not arguing whether git's ui is good or bad, just that S.O. questions are probably a poor yardstick for deciding).

draw_down 10y ago

Not just that, the descriptions you find online of how it works simply don't prepare you for the reality of using it. It's a bunch of boxes and arrows when what you really want is what to do when things inevitably don't work how they are supposed to. I mean, everyone who has written a guide to rebasing must live on Mars. They show how your branch used to point to this box, but now it points to THIS box! And then what you really get when you actually try to use it is a bunch of conflicts between changes that affect files you haven't done anything to and a shit ton of confusion.