Community
Participate
Working Groups
Verified in 1.2.0.201110190928. 1. commit and push some changes to a shared repository 2. in another workspace select a project from the shared repositpory 3. Team > Synchronize Workspace ==> no changes 4. Pull from Upstream ==> it says no ref to fetch from origin This is unexpected since I never did a fetch before. It looks like synchronize operation did a fetch without asking me. This is very bad as I now don't have an easy way to see the list of all incoming commits since my last explicit fetch. Either this side-effect should be removed or put into a preference which is off by default. BTW: Why does synchronize do this but not reset hard?
> Either this side-effect should be removed or put into a preference which is off > by default. Aaah! There is already a preference for this but it is on by default. ==> Disable it by default or ask the user when doing the very first synchronization and then store that preference.
Also, just found Team > Advanced > Synchronize > Customm... In that dialog there is a checkbox for the preference. This could be removed and always use the preference value.
(In reply to comment #2) > Also, just found Team > Advanced > Synchronize > Customm... > In that dialog there is a checkbox for the preference. This could be removed > and always use the preference value. Check box in synchronize wizard is to over roll value set in preference. Is is by default set to value from preferences but it can be changed only for this single synchronization. There are some use cases when you would like to enable/disable fetching changes for on "synchronize session".
(In reply to comment #3) > (In reply to comment #2) > > Also, just found Team > Advanced > Synchronize > Customm... > > In that dialog there is a checkbox for the preference. This could be removed > > and always use the preference value. > > Check box in synchronize wizard is to over roll value set in preference. Is is > by default set to value from preferences but it can be changed only for this > single synchronization. There are some use cases when you would like to > enable/disable fetching changes for on "synchronize session". I see. The problem with this is that dialogs should normally store the previously chosen values. If the one-time only override is really needed then we should add a link to the preference where the default can be configured.
(In reply to comment #4) > I see. The problem with this is that dialogs should normally store the > previously chosen values. If the one-time only override is really needed then > we should add a link to the preference where the default can be configured. I like this idea with link to preference page. IMO dialog shouldn't overwrite stored preferences, we can change check box message to "Fetch changes from remote this time" or something like that.
(In reply to comment #5) > (In reply to comment #4) > > I see. The problem with this is that dialogs should normally store the > > previously chosen values. If the one-time only override is really needed then > > we should add a link to the preference where the default can be configured. > > I like this idea with link to preference page. IMO dialog shouldn't overwrite > stored preferences, we can change check box message to "Fetch changes from > remote this time" or something like that. I think if you have a link to the default then the current text is OK. Take a look at the New Class wizard for example.
Are you sure that projects in those two separate workspace doesn't share same local git repository on your hard drive ? Synchronize operation at the beginning by default fetches changes to show you incoming changes. You can disable this functionality in preferences (Team -> Git -> Synchronize -> Always launch fetch before synchronize).
(In reply to comment #7) > Are you sure that projects in those two separate workspace doesn't share same > local git repository on your hard drive ? > > Synchronize operation at the beginning by default fetches changes to show you > incoming changes. You can disable this functionality in preferences (Team -> > Git -> Synchronize -> Always launch fetch before synchronize). See comment 1.
When I filed this bug I was not aware of the preference, so for me this is no longer a major issue. For new users it would be good though to inform him when he does the very first Team > Synchronize.
