On 22 January 2014 14:39, Alex Shi alex.shi@linaro.org wrote:
I mean LSK has many input resources tree, and if every resource like to maintain a separate and functional tree, while they also cherry pick the same patch, then when revert needed, that is a bit ugly. and that's the Tixy's meaning a bit difficult to maintain. If it is a issue, I want to know why we need keep all input resource trees fast forward only. Do there have specific requests for the fast forward?
It makes life a lot easier making sure the right thing happens when things are merged into the LSK itself if the inputs themselves are fast forward only too (at least the versions of them that are merged into the LSK) and it makes the history of the LSK clearer since otherwise we get multiple copies of the same patch appearing in history (as has happened for the big.LITTLE branch).