From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Junio C Hamano <gitster@pobox•com>
Cc: Thomas Koch <thomas@koch•ro>, git <git@vger•kernel.org>,
Noufal Ibrahim KV <noufal@nibrahim•net.in>,
Andreas Krey <a.krey@gmx•de>
Subject: Re: Command-line git Vs IDE+plugin?
Date: Tue, 19 Nov 2013 18:20:46 +0100 [thread overview]
Message-ID: <vpq1u2c9ukx.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqbo1g9vua.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 19 Nov 2013 08:53:33 -0800")
Junio C Hamano <gitster@pobox•com> writes:
> Perhaps I am being naïve, but I would expect that a GUI is a much
> better vehicle to help users build the right mental model.
One thing the command-line does well is to give names to concepts
(basically, command names, option names, ...). It's easy to write in a
tutorial or an email "run the command 'git foo'". It's less easy to
write "click on that red button, on the right of the green one".
Then, it's clear to everyone what "commit", "rebase", "amend" & so mean,
regardless of the colors of buttons (that's one of the reasons I use the
english words even when I speak french).
That said, even when I teach the command-line, gitk is a very valuable
tool to explain what the DAG is and how branching works.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-11-19 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 17:11 Command-line git Vs IDE+plugin? Matthieu Moy
2013-11-18 17:42 ` Philippe Vaucher
2013-11-18 18:46 ` Matthieu Moy
2013-11-19 9:53 ` Konstantin Khomoutov
2013-11-18 17:47 ` Andreas Krey
2013-11-19 12:36 ` Thomas Koch
2013-11-19 16:53 ` Junio C Hamano
2013-11-19 17:20 ` Matthieu Moy [this message]
2013-12-04 9:56 ` Gauthier Östervall
2013-11-19 16:55 ` Keshav Kini
2013-11-19 12:45 ` Noufal Ibrahim KV
2013-12-04 11:10 ` Chris Packham
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=vpq1u2c9ukx.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=a.krey@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=noufal@nibrahim$(echo .)net.in \
--cc=thomas@koch$(echo .)ro \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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