On 01/22/2014 07:09 PM, Mark Brown wrote:
On 22 January 2014 09:42, Alex Shi <alex.shi@linaro.org mailto:alex.shi@linaro.org> wrote:
BTW, Why we need to keep every topic branch fast forward only? I mean Even in upstream kernel, important tree, like tip/linux-next, are all rebase often.
We don't, but once things have been merged into the LSK itself we need to keep that fast forward only which in turn means that it's at the very least much easier to keep the branches that feed into it fast forward only. If something has only been in -test or not even merged into that then it's definitely OK to just rebase.
Thanks for nice explanation! It's clear LSK need keep fast forward only.
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?