I just noticed that applying the stash in EGit reacts differently than the command line. Say I have an incoming file A which conflicts with my unstaged file A. I stash my file A, rebase and re-apply the stash. I now got file A in staged form which has an undo of the incoming changes and a file A in unstaged form which applies my stash changes. The command line however correctly has a conflict with both changes.
Am I missing something or is this a bug?
The more I work with EGit the more I get the feeling that this plugin is not really production ready. Are there really people working with this plugin on a reasonable sized project? Or is there another eclipse plugin that is more mature than this?
This was fixed recently [1], try a recent nightly build which you may install from [2].
The fix will be contained in the upcoming 2.3 release which will be shipped on Feb 22.
Stash-pull-apply is a common and important workflow for git users.
I only discovered recently that eGit allows you to view stashes in the commit viewer, after months of using the plugin. This is a great feature, but it's completely hidden from users.
As in - you have to know to double-click the stash to view it, and viewing it is not an option when you right-click a stash. I'd suggest including "view stash in commit viewer" as an option in the right-click menu.
Jan Hoskens skrev 2013-02-08 08.57:
> Hi,
>
> I just noticed that applying the stash in EGit reacts differently than the command line. Say I have an incoming file A which conflicts with my unstaged file A. I stash my
> file A, rebase and re-apply the stash. I now got file A in staged form which has an undo of the incoming changes and a file A in unstaged form which applies my stash
> changes. The command line however correctly has a conflict with both changes.
> Am I missing something or is this a bug?