I believe people have finally gotten to grasp with the index. Besides,
those answers are probably a bit skewed, as people that use git as just
a faster and better cvs/svn aren't likely to be those who answer the
survey.
I know myself and most others where I work use it as a 'fixup' command.
One commit is done, the second is being staged (git add or git add -i),
while testing reveals some silly bug in one of the files from the last
commit. Assuming that file isn't touched again, it's easy to fix up
using "git commit --amend <file>", as that automatically sets up a new
index so that the staged changes remain staged.
The alternative would be to do a mixed reset, git add <file>, git commit
--amend. Not so sexy.
Perhaps many who use it don't know that they are. The "git sync"
alias is much in use where I work. It's basically just a
"git pull --rebase && git push". As it was suggested on the mailing
list and also listed in some tutorial somewhere (don't know where),
I can imagine quite a lot of people using it without realising it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html