Community
Participate
Working Groups
The Synchronize wizard should support FETCH_HEAD besides HEAD. This would make it easy to prefetch changes from the remote and applying them one by one. This would be pretty similar to the following scenario: git fetch git://repo.or.cz/stranger.git for-junio git log -p ..FETCH_HEAD git merge FETCH_HEAD Does that make sense? Or should we always fetch the remote changes when synchronizing?
I think we should always fetch remote changes when synchronizing. This does not change the eclipse workspace and does no harm. And it would be what I expect when I call synchronize on a remote branch. However, your proposal makes a lot of sense to me. When you have not fetched a branch but just a commit like for example for gerrit it would be interesting to see the difference between your HEAD and the FETCH_HEAD.
Automatically launching fetch action when remote repository is selected wouldn't be a good solution in my opinion. We shouldn't force uses to have a connection to remote while synchronizing. But from the other hand this would be a great feature if we could give a possibility to "refresh" refs before synchronizing, therefore I think that we should add two new check boxes to synchronization dialog (eg. 'fetch remote data before synchronization'). One for source and one for remote refs. Based on their state the fetch action should be launched or not. With this approach we would have more flexibility and IMHO it is more user friendly and useful.
Change 3403[1] adds additional refs into synchronize wizard http://egit.eclipse.org/r/#change,3403
Merged as commit 6d9384aff46d1329b7c90fad999da5b60b6ded48
