Bug 169409 - [Change Sets] "Consult Change Sets" dialog should be included in commit dialog
Summary: [Change Sets] "Consult Change Sets" dialog should be included in commit dialog
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-01-03 05:34 EST by Markus Keller CLA
Modified: 2019-09-06 16:14 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2007-01-03 05:34:56 EST
I20061219-1300

When I choose Team > Commit from an editor context menu, I always get a dialog asking whether I want to consult change sets.

This additional dialog is disturbing:
- If the resource is not in a change set at all, why do you ask me?
- If the resource is in a change set, I have to choose "Yes" or "No" without knowing which change set I'm going to load.

I see two possible ways to resolve:

a) Only show the dialog if the resource is actually contained in a change set. Add the name of the change set to the message.

b) Inline the functionality into the commit dialog, i.e. add a check box to toggle whether the change set should be consulted. The toggle state should be persisted. Don't show the check box if no change set is applicable.
Comment 1 Michael Valenta CLA 2007-01-03 08:33:24 EST
Inlining the functionality into the commit dialog would probably be the best approach but would also be a large amount of work. As a workaround, you should be able to indicate that you want your decision remembered and you should no longer be prompted.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:14:05 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.