From: Michael Donaghy <mike@mikedonaghy.org>
To: git@vger.kernel.org
Subject: Re: Git Screencast ?
Date: Fri, 23 Nov 2007 18:18:51 -0500 [thread overview]
Message-ID: <fi7n4u$3kc$1@ger.gmane.org> (raw)
In-Reply-To: <20071123101426.GA15902@dualtron.vpn.rwth-aachen.de>
Johannes Gilger wrote:
> On 22/11/07 20:47, Michael Donaghy wrote:
>> Yes thank you , although a screen cast would still be ideal , the
>> documentation is very good,
>> also , what do you think of git-gui ? , I think it is the best one
>
> Hi Michael,
>
> I think you're trying to hide the complexity of git. The problem with
> graphical tools is that they hide complexity from the user, which in
> some cases is only possibly/good if the user has understood the
> underlying principles already. Also I think that there are many things
> which can be done much quicker using a command-line than any gui (as all
> of the people here will agree). Git is not Time-Machine (this thing from
> Apple). It is also no good idea to try to view git from a svn's point of
> view, or try to compare commands. It took me a while to get over that
> and accept that git is different. I was frustated (and still am
> sometimes) but i finally understood the whole concept.
>
> About screencasts: I haven't watched that many screencasts in general,
> but I can hardly imagine that they are better way of teaching things
> than reading a manual. Watching someone type in commands, hitting
> "Pause", then trying it myself doesn't seem more intuitive to me than
> just reading a manual and typing the commands given in regular
> intervals. Maybe someone can enlighten me about the use of screencasts
> (in a command-line environment).
>
> Greetings,
> Jojo
>
I don't know , maybe I learn differently , but
>'Watching someone type in commands, hitting "Pause", then trying it
> myself'
is intuitive for me :)
prev parent reply other threads:[~2007-11-23 23:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 13:02 Git Screencast ? Michael Donaghy
2007-11-21 20:19 ` Johannes Gilger
2007-11-21 21:51 ` Johan Herland
2007-11-21 22:36 ` Randal L. Schwartz
[not found] ` <d411cc4a0711211603o525a25c4i3e04d0319e68204f@mail.gmail.com>
2007-11-26 21:33 ` Scott Chacon
2007-11-26 23:25 ` Christian MICHON
[not found] ` <6b6419750711270602q53e2c51dr7046aca1417c801a@mail.gmail.com>
2007-11-27 14:18 ` Patrick Aljord
2007-11-21 23:45 ` Michael Donaghy
2007-11-22 8:23 ` Andreas Ericsson
2007-11-23 1:47 ` Michael Donaghy
2007-11-23 10:05 ` Andreas Ericsson
2007-11-23 10:14 ` Johannes Gilger
2007-11-23 20:58 ` Shawn O. Pearce
2007-11-25 16:57 ` Karl Hasselström
2007-11-25 17:43 ` Johannes Gilger
2007-11-23 23:18 ` Michael Donaghy [this message]
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='fi7n4u$3kc$1@ger.gmane.org' \
--to=mike@mikedonaghy.org \
--cc=git@vger.kernel.org \
/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).