From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Merge git-gui into 1.5.0 ?
Date: Sun, 11 Feb 2007 03:40:30 -0500 [thread overview]
Message-ID: <20070211084030.GE2082@spearce.org> (raw)
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 reply other threads:[~2007-02-11 8:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 8:40 Shawn O. Pearce [this message]
2007-02-11 14:57 ` Merge git-gui into 1.5.0 ? Mark Levedahl
2007-02-11 22:49 ` Shawn O. Pearce
2007-02-11 16:39 ` Johannes Schindelin
2007-02-11 22:27 ` Junio C Hamano
2007-02-11 22:41 ` Shawn O. Pearce
2007-02-11 22:53 ` Johannes Schindelin
2007-02-11 23:02 ` Shawn O. Pearce
2007-02-11 23:25 ` Johannes Schindelin
2007-02-12 5:40 ` Michael S. Tsirkin
2007-02-12 5:48 ` Junio C Hamano
2007-02-12 5:59 ` Michael S. Tsirkin
2007-02-12 6:25 ` Michael S. Tsirkin
2007-02-12 11:51 ` add negative -p to git-am, " Johannes Schindelin
2007-02-12 11:59 ` Michael S. Tsirkin
2007-02-12 12:06 ` Johannes Schindelin
2007-02-12 12:26 ` Michael S. Tsirkin
2007-02-12 21:55 ` Junio C Hamano
2007-02-12 23:34 ` Shawn O. Pearce
2007-02-12 23:38 ` Johannes Schindelin
2007-02-12 23:42 ` Shawn O. Pearce
2007-02-12 23:53 ` Johannes Schindelin
2007-02-13 0:34 ` Jakub Narebski
2007-02-13 0:38 ` 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=20070211084030.GE2082@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.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).