|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16099) Not able to enter correct S... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)

Another idea: can you identify from the commit history (https://github.com/jenkinsci/subversion-plugin/commits/master) who did break the plugin for you?
Then this one would be the perfect assignee for this issue.