|
||||||||
|
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/d/optout.
Actually I wasn't confusing it at all. The original report mentions nothing about the expected behavior when multiple branches share the same commit, and the scenario I mention easily fits the description.
I commented to help anyone else who might still be running across this issue, and from the comments, it seems like some people might be.
If you're saying I should open up a bug report for this behavior, I can do so. But it sounds like you're not interested in adjusting the behavior. In which case I'll simply provide a workaround if/when I come up with one.