From: David Lang <david@lang.hm>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Sebastian Schuberth <sschuberth@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What is missing from Git v2.0
Date: Tue, 22 Apr 2014 15:25:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1404221523060.14881@nftneq.ynat.uz> (raw)
In-Reply-To: <20140422213039.GB21043@thunk.org>
On Tue, 22 Apr 2014, 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. 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. And we have to
> balance this with the additional cognitive load in remembering how a
> particular two character alias maps to the "real" command. 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.
>
> 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.
>
> 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. 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. 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.
agreed, of all the things that people complain about regarding learning git, the
fact that the commands are words instead of cryptic 2 letter abberviations is
not one of them.
The complaints tend to be far more about how there are inconsistancies between
commands, or they don't understand what's happening.
Adding a new inconsistancy, or changing words to abbreviations is a further
barrier against new users, not an advantage for them.
David Lang
next prev parent reply other threads:[~2014-04-22 22:26 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 22:41 What is missing from Git v2.0 Felipe Contreras
2014-04-20 22:47 ` Felipe Contreras
2014-04-21 19:24 ` Sebastian Schuberth
2014-04-21 19:34 ` Felipe Contreras
2014-04-21 19:47 ` Sebastian Schuberth
2014-04-21 20:45 ` Theodore Ts'o
2014-04-21 20:46 ` Felipe Contreras
2014-04-22 7:23 ` Sebastian Schuberth
2014-04-22 8:15 ` Felipe Contreras
2014-04-21 19:39 ` Junio C Hamano
2014-04-22 7:19 ` Sebastian Schuberth
2014-04-22 8:11 ` Felipe Contreras
2014-04-22 18:33 ` Junio C Hamano
2014-04-22 19:23 ` Felipe Contreras
2014-04-22 20:22 ` Matthieu Moy
2014-04-22 21:01 ` Felipe Contreras
2014-04-22 22:19 ` Junio C Hamano
2014-04-22 21:30 ` Theodore Ts'o
2014-04-22 21:59 ` Felipe Contreras
2014-04-22 22:24 ` David Kastrup
2014-04-24 3:35 ` Felipe Contreras
2014-04-24 5:18 ` David Kastrup
2014-04-24 13:39 ` Andreas Krey
2014-04-24 18:31 ` Felipe Contreras
2014-04-24 19:16 ` David Kastrup
2014-04-22 22:25 ` David Lang [this message]
2014-04-24 3:37 ` Felipe Contreras
2014-04-24 3:51 ` David Lang
2014-04-24 3:58 ` Felipe Contreras
2014-04-24 4:16 ` James Denholm
2014-04-24 4:12 ` Felipe Contreras
2014-04-24 6:06 ` James Denholm
2014-04-24 7:19 ` Felipe Contreras
2014-04-24 7:39 ` David Kastrup
2014-04-24 8:23 ` Felipe Contreras
2014-04-24 9:01 ` David Kastrup
2014-04-24 18:28 ` Felipe Contreras
2014-04-24 19:20 ` David Lang
2014-04-24 13:41 ` Theodore Ts'o
2014-04-24 15:00 ` Stefan Beller
2014-04-24 15:47 ` tytso
2014-04-24 17:46 ` Stefan Beller
2014-04-24 18:02 ` Jonathan Nieder
2014-04-24 18:26 ` Felipe Contreras
2014-04-24 19:15 ` Jeff King
2014-04-24 18:25 ` Felipe Contreras
2014-04-24 18:17 ` Felipe Contreras
2014-04-25 6:59 ` Matthieu Moy
2014-04-25 7:35 ` Philippe Vaucher
2014-04-24 18:38 ` Felipe Contreras
2014-04-24 19:55 ` luc.linux
2014-04-25 2:22 ` Javier Domingo Cansino
2014-04-25 2:35 ` Felipe Contreras
2014-04-25 7:48 ` Philippe Vaucher
2014-04-25 7:52 ` Felipe Contreras
2014-04-25 13:35 ` Theodore Ts'o
2014-04-25 14:23 ` Philippe Vaucher
2014-04-25 14:40 ` Theodore Ts'o
2014-04-25 15:54 ` Philippe Vaucher
2014-04-25 17:50 ` Felipe Contreras
2014-04-25 17:45 ` Felipe Contreras
2014-04-25 18:24 ` Jeff King
2014-04-25 18:27 ` Felipe Contreras
2014-04-25 18:57 ` Jeff King
2014-04-25 18:57 ` Felipe Contreras
2014-04-25 19:12 ` Jeff King
2014-04-25 19:27 ` Felipe Contreras
2014-04-25 5:13 ` David Kastrup
2014-04-25 15:41 ` Jonathan Nieder
2014-04-25 15:59 ` David Kastrup
2014-04-25 16:14 ` Jonathan Nieder
2014-04-22 22:03 ` Junio C Hamano
2014-04-24 3:26 ` Felipe Contreras
2014-04-22 2:12 ` brian m. carlson
2014-04-22 5:10 ` Felipe Contreras
2014-04-22 5:19 ` David Aguilar
2014-04-22 5:38 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1404221523060.14881@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sschuberth@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).