git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Merge git-gui into 1.5.0 ?

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 11, 2007, 08:40 UTC
Message-ID
<20070211084030.GE2082@spearce.org>

One of my goals for git-gui is to get it merged into core Git, so there is a GUI tool available out-of-the-box for commit creation, (some) branch manipulation, basic merging, and pushing/fetching changes.

I'm wondering, should that start to occur as part of 1.5.0? Its one .sh script, like gitk. :)

Given all of the other changes going into 1.5.0, and how much news we're probably going to try to attract to this release, it may be nice to be able to say "we also have a commit creating GUI".

The main idea behind git-gui is to provide a complete enough UI that someone can work on files stored in a Git repository without needing to drop to the command line. By sticking to Tcl/Tk, git-gui is available anywhere gitk is.

It would be nice if all operations available on the command line were also available through git-gui, but I think that is a very difficult goal to reach. The command line interface is simply more powerful and much more expressive. So I'm really just aiming to make an interface that the average user can use to do collaboration through Git, without needing to fall back on git-cvsserver and a CVS client. I fully expect 'power' users to use the command line. You know who you are. ;-)

That said, operations like `git gui blame rev file` may simply be better in the GUI, even for power users, as it offers some way to visualize the annotation data and navigate through it. So I'm also trying to make those parts of git-gui easily available from the command line, when possible.

Another example is `git gui citool` (or `git citool` if git-citool is a symlink/hardlink to git-gui), which will open the UI for just one commit. Users of that-other-SCM-used-before-Git's citool subcommand may like this feature, as it offers somewhat similiar functionality, and some nice extras. ;-)

Right now git-gui is being used in production by myself and about 5 other coworkers of mine (the rest were either die-hard command line users already, or found out how useful the command line is and now refuse to give it up!). It has thus far proven to be pretty stable and easy to use. Its running stably on both Mac OS X and Windows.

It is also lacking the critical `git clone` operation.  ;-)
Thoughts?  Anyone interested can check out the repository:
  gitweb:  http://repo.or.cz/w/git-gui.git
  git:     git://repo.or.cz/git-gui.git
-- 
Shawn.
Next: Mark Levedahl
Message 1 of 24 in “Merge git-gui into 1.5.0 ?”
  1. Shawn O. PearceFeb 11, 2007
  2. Mark LevedahlFeb 11, 2007
  3. Shawn O. PearceFeb 11, 2007
  4. Johannes SchindelinFeb 11, 2007
  5. Junio C HamanoFeb 11, 2007
  6. Shawn O. PearceFeb 11, 2007
  7. Johannes SchindelinFeb 11, 2007
  8. Shawn O. PearceFeb 11, 2007
  9. Johannes SchindelinFeb 11, 2007
  10. Michael S. TsirkinFeb 12, 2007
  11. Junio C HamanoFeb 12, 2007
  12. Michael S. TsirkinFeb 12, 2007
  13. Michael S. TsirkinFeb 12, 2007
  14. add negative -p to git-am, Re: Merge git-gui into 1.5.0 ?Johannes Schindelin, Feb 12, 2007
  15. Michael S. TsirkinFeb 12, 2007
  16. Johannes SchindelinFeb 12, 2007
  17. Michael S. TsirkinFeb 12, 2007
  18. Junio C HamanoFeb 12, 2007
  19. Shawn O. PearceFeb 12, 2007
  20. Johannes SchindelinFeb 12, 2007
  21. Shawn O. PearceFeb 12, 2007
  22. Johannes SchindelinFeb 12, 2007
  23. Jakub NarebskiFeb 13, 2007
  24. Shawn O. PearceFeb 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.