From: Paul Mackerras <paulus@samba.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-gui: A commit / fetch / push interface
Date: Wed, 8 Nov 2006 09:46:47 +1100 [thread overview]
Message-ID: <17745.3287.358673.265578@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20061107083603.GB9622@spearce.org>
Shawn Pearce writes:
> I liked it and wanted to start making it available to some folks I
> work with who are more comfortable with the mouse than they are with
> the keyboard. At first I tried fixing a few of the outstanding bugs
> in gitool but I eventually wound up rewriting the thing from scratch.
Cool!
> I have posted a repository with the source on pasky's service:
>
> http://repo.or.cz/w/git-gui.git
Shouldn't the "w" be "r" there? It gave me an error "Can't lock ref"
with the "w".
> My goal is to have enough operations available through git-gui that
> the average user won't need to leave it, unless he/she needs to do a
> cherry-pick, am, etc. type of operation. Or they want to browse the
> history, in which case they can just start gitk from within git-gui.
> I'm hoping to have most of it done this week. :-)
One thing I have been meaning to do is to integrate gitool into gitk,
now that gitk can display a fake commit showing the local changes. I
intend to add a menu item to gitk saying "Commit local changes" or
something, which would invoke gitool, or maybe now git-gui instead. :)
The nice thing is that then gitk could update the graph to show the
new commit once it was created.
My current version of gitool also has menus that let you revert
modified files, and delete or ignore untracked files. Have you
considered adding that to git-gui?
Regards,
next prev parent reply other threads:[~2006-11-07 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 8:36 [RFC] git-gui: A commit / fetch / push interface Shawn Pearce
2006-11-07 8:58 ` Jakub Narebski
2006-11-07 22:46 ` Paul Mackerras [this message]
2006-11-08 5:46 ` Liu Yubao
2006-11-08 5:55 ` Shawn Pearce
2006-11-08 6:03 ` Shawn 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=17745.3287.358673.265578@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--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).