Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333859 - Spurious year "49" in Date column in History view
Summary: Spurious year "49" in Date column in History view
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-10 07:25 EST by Eleanor Joslin CLA
Modified: 2011-01-11 04:21 EST (History)
0 users

See Also:

Attachments
Screenshot showing part of the History view (25.35 KB, image/png)
2011-01-10 07:26 EST, Eleanor Joslin CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eleanor Joslin CLA 2011-01-10 07:25:36 EST 
Build Identifier: M20100909-0800

I looked at a file in the History view and the date for the latest revision appeared as "08/08/49 15:58".  It should have been "08/12/10 14:58".

I'm in the UK, so these dates are in day/month/year format.  The time was an hour out - a correction for daylight saving?

The dates for other revisions were correct (or at least plausible).  When I looked at the history of another file and then back again, the error went away and I couldn't reproduce it again.

The file is under SVN control and I am using the SVN plugins from tigris.org:

org.tigris.subversion.clientadapter.feature 1.6.12
org.tigris.subversion.clientadapter.javahl.feature 1.6.13
org.tigris.subversion.subclipse 1.6.15
org.tigris.subversion.clientadapter.svnkit.feature 1.6.12

Reproducible: Couldn't Reproduce
Comment 1 Eleanor Joslin CLA 2011-01-10 07:26:34 EST 
Created attachment 186382 [details]
Screenshot showing part of the History view
Comment 2 Tomasz Zarna CLA 2011-01-11 04:21:56 EST 
It doesn't look like a CVS issue, I suggest you open a new bug against Subclipse (http://subclipse.tigris.org/servlets/ProjectIssues).