Issue 2294: Detect changes based on commits that are not in target branch
Status:  New
Owner: ----
Project Member Reported by david.pu...@sonymobile.com, Dec 1, 2013
[1] is pushed for stable-2.6 but is based on a commit at the head of master.  Merging this change will cause all the commits from master to be merged into stable-2.6, which is definitely not a desired result.


[1] https://gerrit-review.googlesource.com/#/c/52313/1

Dec 14, 2015
#1 jrnieder
Setting "Create a new change for every commit not in the target branch" in the project configuration avoids this (https://gerrit-review.googlesource.com/Documentation/project-configuration.html#_use_target_branch_when_determining_new_changes_to_open). Should that be the default?