Re: What is missing from Git v2.0

> Felipe Contreras <felipe.contreras@gmail.com> writes:
> 
> > Theodore Ts'o wrote:
> >
> >> This is especially true for commands which might not be used as often
> >> -- e.g., "rebase", and for commands where the meaning of "git commit"
> >> without any argument is qualitatively different from what "ci" (for
> >> checkin) means in most other source management systems.
> >
> > ci means commit in Mercurial.
> 
> Does it mean "commit the staging area"?

> > It would help when the user starts to think "Geez, I seem to be typing
> > `git checkout` an awful lot, I wonder if there's a shortcut", which if
> > the .gitconfigs out there are any indication, it happens all the time.
> 
> Actually, it happens very rarely if you are talking about _real_
> gitconfigs deployed by projects as compared to _sample_ gitconfigs
> demonstrating Git features for _personal_ rather than project-wide use.

> >> And for a command like "rebase" where the user can very easily shoot
> >> themselves in the foot to begin with, I'd actually suggest that it's
> >> a _good_ thing that they have to type it out in full.
> >
> > And now you contradict yourself; you actually want to make life harder
> > for new users, on purpose.
> 
> Life's hardness is not proportional to the number of typed characters