| Summary: | Need to do two times Team > Synchronize to see the incoming change | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Dani Megert <daniel_megert> |
| Component: | UI | Assignee: | Dariusz Luksza <dariusz.luksza> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | dariusz.luksza, markus.kell.r, matthias.sohn, remy.suen |
| Version: | unspecified | ||
| Target Milestone: | 1.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Dani Megert
This is really bad. I can almost not work with EGit with this bug as I cannot trust the result of Team > Synchronize. Also, it looks like the first (and empty) synchronization actually fetches the stuff from the upstream without notifying me (which would be OK if I would see the changes in the Synchronize view in the first place). > Also, it looks like the first (and empty) synchronization actually fetches the
> stuff from the upstream without notifying me (which would be OK if I would see
> the changes in the Synchronize view in the first place).
Is this a separate bug? If I synchronize on a project in my workspace via 'Package Explorer' (and not the remote master via 'Git Repositories' view), where I understand that I get no changes, the action does a fetch from upstream but nothing is shown to me. When I then do 'Team' > 'Fetch from Upstream', it says there are no changes.
(In reply to comment #3) > > Also, it looks like the first (and empty) synchronization actually fetches the > > stuff from the upstream without notifying me (which would be OK if I would see > > the changes in the Synchronize view in the first place). > > Is this a separate bug? File a new bug 361784 for this. It seams that synchronize doesn't update destination ref after fetching changes. I'll look on this later this week. I've pushed change[1] that should fix this issue [1] http://egit.eclipse.org/r/4402 Verified in 1.2.0.201110251714 that scenario from comment 0 works. (In reply to comment #5) > It seams that synchronize doesn't update destination ref after fetching > changes. I'll look on this later this week. Is this bug 362175? (In reply to comment #7) > Is this bug 362175? Yes, both issues have same cause merged as 9837b9a5e966904ddfd79215ec9cf3cafcb58cdc Thanks! Verified in 1.2.0.201112061823. |