From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Steffen Prohaska <prohaska@zib.de>, git@vger.kernel.org
Subject: Re: [PATCH] user-manual: mention git gui citool (commit, amend)
Date: Sat, 4 Aug 2007 10:35:59 -0400 [thread overview]
Message-ID: <20070804143559.GC10294@fieldses.org> (raw)
In-Reply-To: <20070804062010.GQ20052@spearce.org>
On Sat, Aug 04, 2007 at 02:20:10AM -0400, Shawn O. Pearce wrote:
> But at this point in git (and git-gui's) life I think it would
> be very worthwhile to devote an entire (new) chapter to git-gui,
> maybe as part of git 1.5.4/git-gui 0.9.0. I think we're far too
> late in the 1.5.3 cycle to do it now. I personally won't have the
> time to even try to rough draft something anytime soon, let alone
> let others copy-edit me before Juino releases 1.5.3. :)
>
> Being bundled with core git has brought git-gui a sizeable and
> growing userbase, and more and more users are discovering it
> each day. We're now seeing it be translated into many different
> languages, and it is a somewhat core part of the MSYS port as many
> Windows users prefer to click in GUIs over type in cmd.exe terminal
> windows (can't say I blame them, cmd.exe is aweful!).
>
> In other words I think git-gui should get roughly as much attention
> from the user manual as git-add/rm/mv/commit/checkout/branch get,
> as it offers the same feature set. But it shouldn't distract from
> the command line part of the manual.
>
> Maybe we should write parts of the manual in a "choose your own
> adventure style" and use different chapters for different paths.
> I think users can easily decide between the command line "i like to
> type" vs. the gui "i like to click" paths and focus their attention
> to the material they are most interested in. :-)
Sure.
For now, though, I think it'd be simplest to start with an entirely
separate appendix. And find a way to make links to that chapter are
prominently featured in Windows ports, as that sounds like an immediate
need.
And then later as git-gui progresses we can figure out how to integrate
it better.
--b.
next prev parent reply other threads:[~2007-08-04 14:36 UTC|newest]
Thread overview: 36+ 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
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 [this message]
2007-08-05 12:26 ` Steffen Prohaska
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 3:33 Brett Schwarz
2007-08-06 4:06 ` Shawn O. Pearce
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=20070804143559.GC10294@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
--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).