Re: What is missing from Git v2.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Theodore Ts'o wrote:
> On Tue, Apr 22, 2014 at 02:23:18PM -0500, Felipe Contreras wrote:
> > > I am not fundamentally opposed.  I just do not think it would add
> > > much value to new people at this point, and it will actively hurt
> > > if we shoved barely cooked one in 2.0.
> > 
> > You are probably biased in that you've used Git far much more than
> > the average user has (or future new users).
> 
> I think Junio has a really strong point.

What is that point?

> If the goal is to make life easier for new users, allowing them to save a few
> keystrokes is probably not the most significant thing we can do.

No, but it's *one* thing we can definetly do, and since we are not doing
anything else, we might as well do this one thing.

> And we have to balance this with the additional cognitive load in remembering
> how a particular two character alias maps to the "real" command.

What cognitive load? You don't *need* to remember the default aliases; you
don't need to use them at all.

> 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.

> So I do think it's worth thinking about this very carefully.  For
> certain, I would **not** recommend using shortcuts in example command
> sequences.  If the user reads "git rebase" or "git cherry-pick" it
> means a lot more than if they see a series of apparent chicken
> scratches filled with things like "git rb", "git pi", "git st", etc.

Certainly, but that is orthogonal.

> In fact, to be fair, you may be getting biased because you're used to
> using the two character shortcuts, so for you, of *course* "rb" and
> "pi" and "ci" make a lot of sense.

I can't be biased to those because I don't use them, mine are one character
shortcuts.

And if that hypothesis was correct, why does Mercurial, Bazaar, Subversion,
CVS, and pretty much everything uses aliases? And why does pretty much every
.gitconfig has similar aliases? That would imply that the whole world is
biased.

> But for someone who is starting from scratch, I really question how much it
> helps, and how much it might hurt, to see the two character shortcuts or even
> to have to remember the two character shortcuts.

Here you are talking from your own bias.

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.

> 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.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]