|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello,![]()
First of all… I am not your enemy… so words about loose ideas to work with revision instead of timestamps… “you messed up with timestamps” … perhaps not so nice…
Anyway…
1. I think you are mistaken. What this lines are saying is: when subversion cannot fully read and understand the timestamp, but understands it partially, it assumes that time is 00:00 (midnight) of that day. You, in your request may not mean it, right?
2. I did not delete any timestamps. I checked all the repos I am administering several thousand revisions back – all timestamps are there. Yes, they can be changed. I personally never did it for any single timestamp in any repo I am administering. Users…. might however.
3. I made my point clear many times already – timestamp are difficult to deal with and they cannot be reliable in making decision whether or not to run build. Besides, it is not efficient to use timestamp to search repo if any revision were made for this particular place in repo between these two timestamps – too much work… revisions are better and more clear defined properties to deal with, so I am proposing to make changes in the code and get rid of this approach with timestamps and use revision numbers instead.
Regards,
Slava