|
||||||||
|
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-14201) Git submodules che... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... [email protected] (JIRA)

I'm sorry, that I'm wrong about the cause of this problem.
git fetch -f is executed when subtree merge done.
I investigated and compared the result with my {clone, submodule init, submodule update} and git-plugin's {clone, fetch -f, ...}.
This is of course still problem, but my guess is entirely wrong, I'm sorry.