[Toaster] Unable to rebase

[Damian, Alexandru]

Dave,

I'm gonna try to make the rebase painless, with a new toaster/master push.

I am aware of this rebase work, so I'm suggesting that any minor fixes can
be open as bugs instead of holding up the review process.

So I propose that we do the merging today, since you'll ping me in the
morning your time anyway.

Does this sound ok to you ?

Alex


On Thu, Jan 30, 2014 at 10:23 AM, Barros Pena, Belen <
belen.barros.pena at intel.com> wrote:

>
>
> 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
>
>


-- 
Alex Damian
Yocto Project
SSG / OTC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20140130/0c0e1b0a/attachment-0001.html>