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.
IMHO, the CVS Status Ouptput is designed in the way that user expect different execution of Diff command then it is then executed. There are Working rev: , Repos.Rev: txtFields , Diff button in one row so thus I'm realy expect thet Diff will be performed beatween those 2 revisions: work(in fact the localy modif.) & repo Reproduction: ============= Have some out-dated files. In my case it was CVSRoot.java from org.netbeans.lib.cvsclient package. And it was 1.3 Revision. But in repository has been already 1.6 which I get to know by running CVS->Status on that file. This Status Output dialog has Diff button just next to those to revisions field. So I thought I could get differencies between those to revisions (or in fact between local version against latest HEAD rev.). But what was the surprise I've got the result: No differencies has been found... This Diff commands is executed without any rev.parametrs which I think is in conflict of design logic's dialog.
I agree, I'd expect this: Working rev: [1.3___] [View Diff], Repos.rev: [1.6___] [View Diff] | | -- shows diff againts repository 1.3 | | shows diff against repository 1.6 -- IMHO, the current implementation associates "View Diff" button with Repository revision, but functionally it is associated with Working version version. BTW: If there's an easy way, how to provide information that the working revision was really modified, it would be nice to have that information immediately when dialog appears. If it means, that you have to connect to the far repository, then don't provide that information.
Actually, I thing that this is a good idea. It's easy to make the first [View Diff] button enabled only when the local file is modified and the second [View Diff] button enabled only when the revision numbers are different.