| Re: [egit-dev] Editing a file several revisions back |
There was a discussion a while ago in some forum (can't recall where) with different opinions.
My vision is to reuse the history view and allow the user to just drag the revisions to the
order s?he wants. Egit can calculate expected conflict even before the rebase starts.
Seeing ungit make me even more convinced that direct manipulation is the right approach rather
than introducing another view. It might be that the history view need to be
redesigned completely for the integration to work. That said, I don't have a patch,
so the honor goes to the one that actually does something about it.
Other than that I'm not very happy with EGit in the current incarnation. Git operations are spread
out all over the place and almost everything is called something non-gitish so it does not work well as a
learning tool using it is slower than using the command line. That's not becuase EGit itself
is slower, which it is, but only very little. The overhead is in navigating to the operations
and remembering there the operation is. Compare this with pressing the up-arrow to recall a
previous command and editing it slightly. Most git operations are like this.
A Gui should be much _easier_ to use than the CLI. There is a thread on the GitML list about Git gui's.
That's where I learned about ungit btw from Junio's post.