[Toaster] Unable to rebase

Barros Pena, Belen belen.barros.pena at intel.com
Thu Jan 30 02:23:48 PST 2014



On 29/01/2014 19:28, "Lerner, Dave" <dave.lerner at windriver.com> wrote:

>Hi Alex, Belen
>
>After Alex's push upstream and a local rebase, it seems that I will have
>to go through a third major rebase effort.
>
>I would like my next push to be quickly added upstream so that I don't
>have to churn on rebasing once again.

I'll try to speed up the review process. The problem I have is that, in my
experience, it pays off to fix as many issues as possible before merging
to a master branch (toaster/master in our case). The moment code is merged
to master, it seems to become necessary to raise issues using the bug
tracking system, which results in the number of issues ballooning up. I
don't have a problem with that, but people having to fix the issues might
find it difficult to decide what to do first: fixing problems from
previous features or tackling new features.

I am copying everybody because this is very much a process problem: it
would be good to hear what everybody else thinks.

Cheers

Belén

>
>Thanks,
>Dave 



More information about the toaster mailing list