This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I don't think cvs commit be enabled for an up to date file. I don't think cvs remove be enabled on a file which has never been added or committed.
Commit should be enabled on Up-to-date files also. You are still able to commit a new revision by turning "Advanced Options" to true and checking on "Force to Commit". Remove really does not have sense on [Local] files. Changing product to vcscvs, since CVS support is not built in vcsgeneric.
This should be done in a consistent way for all commands. If people from the CVS team think about other combination of other enabled/disabled commands, please write it to this issue. IMO no CVS commands have sense on [Local] files with the exception of CVS->Add. Therfore we should perhaps remove the whole CVS->... menu and replace it by "CVS Add" for [Local] files. What do you think ?
I propose these situations: Status of the file Disabled commands -------------------------------------------------------------------------- [Locally Removed] Remove, Diff Graphical, Diff Textual, Export [Needs Checkout] Commit, Export, Diff Graphical, Diff Textual [Locally Added] Check Out, Export, Diff Graphical, Diff Textual, Tagging, Editing, Watching and Locking, Patch [Needs Patch] and [Needs Update] probably the same as for [Needs Checkout] What do other guys think ?
Well, I would do some further modifications to this: Status of the file Disabled commands -------------------------------------------------------------------------- [Locally Removed] Remove, Update [Needs Checkout] Commit [Locally Added] Tagging, Editing, Watching and Locking [Needs Patch] and [Needs Update] the same as for [Needs Checkout]. I've removed Diff Graphical, Diff Textual, Export and Patch, because they can work on other revisions of the file, than that in the working directory. Even [Locally Added] file can exist on different branches. Comments ? Do you think, that this is complete ?
Martin, I don't think this is complete. Earlier in this thread you mentioned [Local] Status of the file Disabled commands -------------------------------------------------------------------------- [Local] [All but Add] <-- wait, can't a user still also do graphical or textual diffs as well? I wouldn't recommend getting rid of all the other commands, i'd just disable them
The general rule for disabling vs. removing commands (or objects) is this. If there is some (reasonably local) action that the user can take in order to re-enable the command/object, then it should be disabled, not removed. However, if nothing the user can do will re-enable the command/object, it should be removed. (Some users will go nuts trying to figure out how to re-enable a command/object if it cannot be re-enabled.) So in general I agree with Ann. However, having only an amateur's knowledge of CVS, I am not qualified to decide whether any commands should be removed instead of disabled.
More like an enhancement than a bug.
UI keyword added.