Don't offer Retry when a merge has conflicts
Bug #529958 reported by
Ian Clatworthy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QBzr |
Confirmed
|
Low
|
Gary van der Merwe |
Bug Description
The recently added Retry button when a command fails is nice. The only problem is that it gets displayed unexpected now and then, e.g. when a merge has conflicts. In this case, I don't expect to see Retry because there doesn't seem any reason to try running the command again. If that's the case, I think the dialog should just offer Close.
Changed in qbzr: | |
assignee: | nobody → Gary van der Merwe (garyvdm) |
status: | Confirmed → In Progress |
Changed in qbzr: | |
status: | In Progress → Confirmed |
To post a comment you must log in.
It would be great if the retry button can be replaced with:
"merge conflicts..." when conflicts happen on merge and update dialogs;
"update" when committing on a bound branch when the server and client revisions differ; (NB: for me :) )
"commit changes..." when trying to merge when there are uncommitted changes in the local branch.
This would make it easier for the user, since he/she would not have to close the dialog kick off another dialog then open it again. I run into this alot with bound branches commit and update etc. This usually gets my colleges swearing under their breath :)
I know this might introduce alot of complexity but I think it would greatly improve the user experience.