Bug 66027 - [Tags] Problems comparing by date
Summary: [Tags] Problems comparing by date
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-06-07 14:28 EDT by DJ Houghton CLA
Modified: 2019-09-06 16:19 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2004-06-07 14:28:44 EDT
build i0604-1200

- created date Dec 12, 2002
- created date Sept 26, 2002
- using the CVS repos view I went to Dec 12, 2002 -> org.eclipse.core.resources
- context menu: Compare With.. -> Date -> Sept 26, 2002

-> I got a dialog saying that there were no changes
-> I also got an error dialog from CVS. In the details message it had the
following info: 

osgi> !SESSION Jun 07, 2004 14:23:46.12 ----------------------------------------
eclipse.buildId=I200406041200
java.fullversion=J2RE 1.4.1 IBM J9 build 20040510 (JIT enabled)
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -showlocation
!ENTRY org.eclipse.team.cvs.core 4 -10 Jun 07, 2004 14:23:46.72
!MESSAGE The server reported an error while performing the "cvs rdiff" command.
!SUBENTRY 1 org.eclipse.team.cvs.core 4 -14 Jun 07, 2004 14:23:46.72
!MESSAGE : cvs [server aborted]: second date must come after first date!

I would expect to be able to select the dates in either order.
Comment 1 Jean-Michel Lemieux CLA 2004-06-07 16:40:01 EDT
You will have to compare them in the other order, as the message says :) We
can't do much about this, except maybe precheck the tags we send. Post 3.0.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:19:11 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.