|Re: check in/out problem [message #754212 is a reply to message #754102]
||Tue, 01 November 2011 12:49
| R Shapiro
Registered: June 2011
In my experience there are two main reasons to use the Synchronization perspective in Subclipse. One is to review local changes before committing them, the other is to review incoming changes. For anything else it's more efficient to run the SVN operations from your primary development perspective (Java, C++, whatever). I've watched a number of developers switch to the Synchronization perspective just to do a blind svn update or commit, without any kind of review. I have no idea why they do this, I'm guessing they were taught to do it that way and never looked further.|
To review before committing in egit, I strongly recommend the 'Git Staging' view.
To review incoming changes (ie, fetched or pulled) you can get at the incoming commits from the modal popup that appears when the egit operation completes, and open any given commit in its own window for more details. Might be nicer if this commit list weren't modal -- this was discussed in another thread. But it works ok as it is.
You should also ensure that the 'Git' command group is enabled in your primary perspective. This will give you menubar and/or toolbar support for all the fundamental operations: Add, Commit, Checkout, Rebase, Reset, Push, Pull, Fetch,
That doesn't leave much for the Synchronization perspective except branch/reference comparisons. In small repositories this works pretty well. For large ones, or any size repo with a very long history, it's pretty slow.
A feature I'd really like to see in egit is the equivalent of 'git log B1 ^B2', that is, a list of commits in one branch/reference but not another. This is generally a very fast operation on closely related branches and is extremely useful. If I could get the result as a view containing a list of commits, somewhat like the 'Git Reflog' view, that would be a huge win.
Powered by FUDForum
. Page generated in 0.02489 seconds