We are using subversion as our repository, and have indexed starting from about 18 months ago. I was 3 years old in 1969, so I am sure I did not make a commit at that time. What gives?
fisheye svn commits.PNG
It appears the bad commit is the one Fisheye created when I imported the repository:
Sorry. The initial import commit is a synthetic commit created to capture the state of the repository at the point of the initial import. It's date is set to the epoch date because it needs to have a value and this value should keep it out of the way of the real commits in the repository.
Does this cause a problem?
It would seem that some of your commits do not have dates and FishEye applies the Java "epoch" date which is 1-Jan-1970. I guess this is then being time zone adjusted into 1969.
Can you check the commit that is showing up in that time region and then have a look at it in Subversion to see why it might not have a date.
We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events