git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Tue, 20 May 2008 22:46:01 +0200	[thread overview]
Message-ID: <bd6139dc0805201346g411c7d64i16d206953e595b38@mail.gmail.com> (raw)
In-Reply-To: <20080520203153.GH29038@spearce.org>

On Tue, May 20, 2008 at 10:31 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> 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.

Heh, I've never understood that, but I have a classmate that won't
touch anything that doesn't have a "shiney" GUI that he likes (that
is, he'll prefer the program with a "shiney" GUI even if there is one
without that has better features).

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

Is it "shiney"? If you haven't already, look into applying a theme to
the app, the Substance LAF definitely looks "shiney"!

> Yes.  I'll send Junio a patch for Documentation/git-gui.txt and
> describe it as a debugging option, and also mention that the commands
> it displays aren't all meant to be invoked by mortals.

Sounds like a plan (maybe use "mere mortals" instead ;), it's more cool).

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2008-05-20 20:47 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 [this message]
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
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=bd6139dc0805201346g411c7d64i16d206953e595b38@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newsletter@dirk.my1.cc \
    --cc=spearce@spearce.org \
    --cc=sverre@rabbelier.nl \
    /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).