Bug#781292: unblock: binutils/2.25-6

[Matthias Klose <doko@debian.org>]

On 04/13/2015 03:55 AM, Michael Gilbert wrote:
> On Sun, Apr 12, 2015 at 9:36 PM, Matthias Klose wrote:
>> because upstream backport patches were done by component for the 2.25 branch,
>> and don't have any equivalent to the single patches on the trunk.  Feel free to
>> prove me wrong.
> 
> That wasn't really the point.  The point was more about why not keep
> the existing patches untouched, but add a final diff that could
> possibly be reviewable.

so you would feel better if I create my own diff to the current state of the
branch, from the point where I stopped backporting patches?  How would you
review these?

>>> Please resist the urge to count lines of the diff
>>
>> no, you couldn't resist :-/
> 
> The size of course is important because as is it's basically an
> unreviewable change,

so these are all changes related to security issues raised by the security team.
 It is this size.  Could you explain how these can be made reviewable?  If you
look at the upstream commits, these are all done in sequence, so you can split
these into patches done for one component. But again, how would that make review
easier?

> which is why no one from the release team is
> looking at it, and why stands little chance for making it into jessie.

at least good to know that the release team isn't looking into it, although a
confirmation on their own would have been nice.

> Anyway it's not my call, I was just trying to help.

thanks, it is appreciated.

Matthias