|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Hello,
I filed bug here and you have responded, I was assuming you are a developer for svnkit. I am sorry if you are not... then I am not sure why I was having all this discussing with you. I am not java developer and so, not going to make any changes to this code.
I am not sure also what kind of advantages this approach using timestamps can provide - to me it is not efficient and causes problems.
as you stated previously, I am not the first one who files this problem. so, problem does exist and needs to be fixed.
like I said in my previous email: when this happened, our build engineer manually runs svn command and it goes just fine. so, to me it indicates that problem is not in svn, but in svnkit.
if you cannot fix it in svnkit code... why did you reply then?
regards,
Slava