|
||||||||
|
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.

From http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html, emphasis mine:
Since branches are just directories, just like anything else in a repo, it makes sense from a tools perspective to assume one level of directories are branches, and not recurse. Aside from the performance issue, you'd need to offer every possible directory in the repository as a possible branch root directory.
I think you'll also have a difficult time creating those Git-style branches in the first place except by manually creating the feature parent folder separately (which should give you a hint as to how well-supported this is in the first place).
Different tools work differently, so arguing that it works in Git leads you nowhere.
Not a bug IMO, and not something that needs support in the first place.