[yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

[Alexander Kanavin]

On 12/11/2017 08:13 AM, Robert Yang wrote:

>> I think it's a simpler and easier to understand approach. Yes, this 
>> means that an updated recipe that is close to the root of dependency 
>> tree can cause a cascade of build failures (e.g. glibc), but the 
>> update commits for everything else will still be created, and the 
>> maintainer can easily revert the failing updates, and re-run the 
>> build. What you think?
> 
> Yes, since glibc would causes others failed to build, so I removed the 
> commited
> during upgrading, and then apply it back, I think that this is more 
> helpful than
> leave the failed commit there and causes others failed.

How about simply issuing 'git revert' after a build has failed? That's 
easier to implement than rearranging the order of commits, and the 
commit message can include a link to the build failure logs.

Alex