This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2/3 elf] Add MicroBlaze support to elf.h


On Thu, Nov 29, 2012 at 11:19 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Thu, 29 Nov 2012, Carlos O'Donell wrote:
>
>> The indirect benefit is that we get the community into the
>> habit and discipline of setting aside trivial changes to
>> focus on stabilizing trunk.
>
> The freeze is meant to be our servant, not our master.  A freeze causes
> harm by preventing useful improvements getting in, being used as a basis
> for other improvements and becoming available to users of releases, and
> should be strictly limited so that it only operates to the extent, and for
> the time, necessary to get out a release maximally useful to a wide range
> of users on a range of architectures.

[trimming CC]

I find it difficult to quantify how much harm is done by
preventing these improvements from going in today.

Yet I find it easy to quantify how much harm is done by
not working on P2 bugs for 2.17 (opportunity cost paid
by working on something else).

Thus when I balance "Potential future harm because
feature X is not in 2.17" versus "Potential future harm
done by bug fix X not in 2.17", I always find the latter
is more important.

How do these two balance out in your own judgement?

I'm not judging your decisions, I'm just trying to understand
your viewpoint.

You are always free to work on the things you find important.

Cheers,
Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]