From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Thu, 22 May 2008 21:55:57 +0100 [thread overview]
Message-ID: <320075ff0805221355y6d5dd4dcgdd12fad9582ea588@mail.gmail.com> (raw)
In-Reply-To: <20080520203153.GH29038@spearce.org>
> I'm not worried about users leaving git-gui. Hell, if git-gui
> was just git on training wheels and all git users left git-gui
> after a while for the command line that would be telling as it
> says the graphical interface is not desired. Or that git-gui's
> interface is not well suited to the task.
>
> Far from it. Some users like git-gui for its ability to show
> the modified files, and let you stage/unstage individual hunks.
> Others like its ability to perform checkout+pull in one mouse
> click. Many like to point at things with a rodent than to use
> the keyboard and enter (to them) isoteric commands.
>
> Right now there are really only two git GUIs; git-gui and QGit.
> Each has its strengths. Maybe this time next year we will have
> a 3rd; name yet to be determined but it would come out of the
> egit/jgit project as a stand-alone SWT/Java based Git UI.
>
I have to say - git is the first SCM that I've used that commandline
usage is actually pleasant in - so much so, the lack of easy cut&paste
from 'git status' in colleagues cygwin windows becomes a serious pain!
git-gui is good though - but there's a few things I wish it had. I
often find the need to flip between git gui and gitk (for a 'where the
heck am I at the moment' overview) - the 2 tools seems to confuse
people coming at git, even given 'visualize branch'. It'd be nice to
be able to add files / directories to .gitignore, and to view the
staged/unstaged changes as trees - helpful for when a build has
created a non-ignored directory with thousands of files. Maybe I
should get qgit - but git gui has the massive advantage of being in
every install by default, and so is available in msysgit.
Whilst I'm thinking about it - I'm surprised in retrospect how little
prominence the index is given in the frontends I've seen. It's easy,
coming from SVN, to gloss over the index as the same as just checking
off files at commit time, and miss stuff like 'git add --patch' and
'git mergetool' altogether.
next prev parent reply other threads:[~2008-05-22 20:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 12:03 git gui: Possible to see which commands are executed? Dirk Süsserott
2008-05-18 12:13 ` Miklos Vajna
2008-05-18 12:34 ` Dirk Süsserott
2008-05-19 2:21 ` Shawn O. Pearce
2008-05-20 19:03 ` Dirk Süsserott
2008-05-20 19:44 ` Shawn O. Pearce
2008-05-20 20:05 ` Sverre Rabbelier
2008-05-20 20:17 ` Shawn O. Pearce
2008-05-20 20:22 ` Sverre Rabbelier
2008-05-20 20:31 ` Shawn O. Pearce
2008-05-20 20:46 ` Sverre Rabbelier
2008-05-20 21:34 ` Junio C Hamano
2008-05-21 2:41 ` Shawn O. Pearce
2008-05-21 8:30 ` Johannes Schindelin
2008-05-21 9:27 ` Karl Hasselström
2008-05-22 12:12 ` Shawn O. Pearce
2008-05-22 20:55 ` Nigel Magnay [this message]
2008-05-22 23:05 ` Shawn O. Pearce
2008-05-20 20:12 ` Dirk Süsserott
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=320075ff0805221355y6d5dd4dcgdd12fad9582ea588@mail.gmail.com \
--to=nigel.magnay@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).