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. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
