|
||||||||||||||
|
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.
I don't think there is much hope of duplicating this issue 18 months after it was reported. I didn't see this problem even back when it was reported (as far as I can recall).
The Git plugin has been through major revisions since the bug was first reported. It still uses the same basic mechanism for cloning as it did at the time this bug was reported, and it still has many hundreds of users on Debian machines.
If the original submitter can still duplicate the bug, hopefully they can provide additional information on how to configure a system that will show the bug.