944b838d88
Introduce a branchOrder section in the project.config in order to define a branch order and automate the back/forward porting of changes. For now assume only one branchOrder section. For example: [branchOrder] branch = master branch = stable-2.9 branch = stable-2.8 branch = stable-2.7 This format makes the ordering obvious (top-down) and complete: for any two branches from the list the order is defined. The --other-branches will rely on the branchOrder section in order to find out a set of branches for which to check mergeability. With the above example, If a change is pushed to the master branch then the --other-branches option will test mergeability into the stable-2.9, stable-2.8 and stable-2.7 branches. If the changed would be pushed to the stable-2.8 then the --other-branches option would test mergeability only into the stable-2.7 branch. Change-Id: Ib806d7e4b5702fa2d8effd197829b729cad95432 |
||
---|---|---|
.. | ||
src | ||
BUCK |