git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Steffen Prohaska <prohaska@zib.de>,
	gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH v2] user-manual: mention git gui citool (commit, amend)
Date: Mon, 6 Aug 2007 15:43:27 -0400	[thread overview]
Message-ID: <20070806194327.GE24946@fieldses.org> (raw)
In-Reply-To: <200708062136.50462.robin.rosenberg.lists@dewire.com>

On Mon, Aug 06, 2007 at 09:36:49PM +0200, Robin Rosenberg wrote:
> Who reads manuals for GUI's? Rougly nobody, unless the user needs the gui 
> badly AND the GUI sucks badly. Manuals for GUI's are mostly tick-in-the-box 
> documentation (which is the probably reason most GUI documentation suck too).

I tend to agree.  But the goal for now isn't to provide complete
documentation, it's just to briefly point out the existence of this tool
and what it does.

I haven't used it myself other than just to experiment a bit, but my
impression from the people involved is that they still consider it a bit
young, but that they think it's useful and that they'd benefit from more
people trying it out.

--b.

  reply	other threads:[~2007-08-06 19:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 16:11 [PATCH] user-manual: mention git gui citool (commit, amend) Steffen Prohaska
2007-07-31  0:24 ` Shawn O. Pearce
2007-08-02 18:18 ` J. Bruce Fields
2007-08-02 22:24   ` Steffen Prohaska
2007-08-02 22:31     ` J. Bruce Fields
2007-08-03  5:08       ` Steffen Prohaska
2007-08-03 12:56         ` J. Bruce Fields
2007-08-05 12:59           ` [PATCH v2] " Steffen Prohaska
2007-08-05 13:58             ` Johannes Schindelin
2007-08-05 14:17               ` Steffen Prohaska
2007-08-05 14:48                 ` Johannes Schindelin
2007-08-05 15:03                 ` David Kastrup
2007-08-05 19:47                   ` Steffen Prohaska
2007-08-06  0:22                     ` Johannes Schindelin
2007-08-06  5:20                       ` Steffen Prohaska
2007-08-06  9:36                       ` Steven Grimm
2007-08-06 11:51                         ` Johannes Schindelin
2007-08-05 22:22               ` J. Bruce Fields
2007-08-05 22:25                 ` J. Bruce Fields
2007-08-06  0:26                 ` Johannes Schindelin
2007-08-06  3:51                   ` J. Bruce Fields
2007-08-06 19:36                     ` Robin Rosenberg
2007-08-06 19:43                       ` J. Bruce Fields [this message]
2007-08-03  3:01     ` [PATCH] " Shawn O. Pearce
2007-08-03 12:56       ` J. Bruce Fields
2007-08-04  6:33         ` Shawn O. Pearce
2007-08-05 12:09         ` Steffen Prohaska
2007-08-03  0:05   ` Junio C Hamano
2007-08-03  3:04   ` Shawn O. Pearce
2007-08-03 12:58     ` J. Bruce Fields
2007-08-04  6:20       ` Shawn O. Pearce
2007-08-04  7:44         ` David Kastrup
2007-08-04 14:35         ` J. Bruce Fields
2007-08-05 12:26         ` Steffen Prohaska

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=20070806194327.GE24946@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=prohaska@zib.de \
    --cc=robin.rosenberg.lists@dewire.com \
    /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).