No, the patch only changes the behavior for the case where there is a merge target. The merge target branch is a reasonable reference for new (not built before) branches - Without it what would you consider a reasonable reference? From your comment 9/Jun/12 12:03 it is clear that you would want the changeset to be relative to 'master', but 'master' is just another branch to git. How should it know that you want change sets to be computed relative to 'master'?

A change that could serve both of us would be to add a configuration option to the git plugin where you can specify that you want changesets to be computed relative to a named branch, ie you would have to check a box "Compute changesets relative to named branch" and fill in the name of the branch. That would work for both of us.

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

Reply via email to