From: David Kastrup <dak@gnu.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Alexandre Bourget <alexandre.bourget@savoirfairelinux.com>,
Git Mailing List <git@vger.kernel.org>,
paulus@samba.org
Subject: Re: [PATCH] Mod. gitk to support REBASE (with stash support).
Date: Thu, 09 Aug 2007 07:51:08 +0200 [thread overview]
Message-ID: <85odhhntmb.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20070809032610.GA24573@spearce.org> (Shawn O. Pearce's message of "Wed\, 8 Aug 2007 23\:26\:10 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> David Kastrup <dak@gnu.org> wrote:
>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> > General question: should this not be in git-gui rather than gitk? Gitk as
>> > of now is really more a viewing tool.
>>
>> Well, yes. But git-gui only works on a single branch head at a time,
>> and that is not enough for rebasing.
>
> Sure. But so does git's command line tools. They tend to only
> work on a single branch at time, the one called `HEAD`.
"tend", and many accept an explicit override: rebase accepts three
commit names, for example. Those that _write_ into the repository
usually _end_ up at HEAD, but most need not start there.
And git-gui does not have any operation either looking at or working
other than on the current HEAD. No diff, no file view, no rebase,
nothing.
> So "single branch head at a time" is *not* why git-gui doesn't
> support rebase. Its because nobody has gotten around to writing it.
I never claimed that it is not possible to put a rebase in there (the
patch does this, after all). I just said that it does not _fit_ in
there since you can't actually look at what you are rebasing on.
>> Could git-gui perhaps be merged with giggle at some point of time?
>
> Unlikely. A while ago I considered "Stay in Tcl/Tk or move to
> something more 'powerful/better/faster/Linus friendly'" and stayed
> in Tcl/Tk. I doubt git-gui will leave Tcl/Tk. giggle is Gtk based.
My bad: git-gui has a nice polished look on my systems (Ubuntu Feisty)
while gitk has an ugly retro-blockish old-font Tk look; so not looking
at the innards, I had assumed they were implemented using different
systems.
> I decided that any sort of rebase operation in git-gui must be *at
> least* as easy to use/user friendly as `rebase -i` is. Anything
> less is just mocking the end-user. Or something like that. Anyway,
> since git-gui is restricted to a graphical interface and most such
> interfaces have these pointy rodents available we can do fancy
> things like dragging to express what we want to have happen, instead
> of moving lines of text around.
>
> Want to write a patch (or series of patches) for git-gui?
User interfaces are really not what I am good at, and I don't even
have enough time to deal with the things I am good at.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-08-09 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 18:33 [PATCH] Mod. gitk to support REBASE (with stash support) Alexandre Bourget
2007-08-08 19:31 ` Peter Baumann
2007-08-08 19:42 ` Johannes Schindelin
2007-08-08 20:08 ` David Kastrup
2007-08-09 3:26 ` Shawn O. Pearce
2007-08-09 5:51 ` David Kastrup [this message]
2007-08-09 6:58 ` Shawn O. Pearce
2007-08-09 7:21 ` Shawn O. Pearce
2007-08-09 7:55 ` David Kastrup
2007-08-08 19:53 ` Junio C Hamano
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=85odhhntmb.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=alexandre.bourget@savoirfairelinux.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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