This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Updated GCC vs Clang diagnostics


On Fri, Apr 13, 2012 at 11:36 AM, Gabriel Dos Reis
<gdr@integrable-solutions.net> wrote:
> On Fri, Apr 13, 2012 at 10:30 AM, NightStrike <nightstrike@gmail.com> wrote:
>> On Fri, Apr 13, 2012 at 11:22 AM, Gabriel Dos Reis
>> <gdr@integrable-solutions.net> wrote:
>>> On Fri, Apr 13, 2012 at 9:23 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>>>
>>>> Shooting down a potentially user friendly feature to wait until some blue
>>>> sky redesign is implemented means it might never be implemented.
>>>
>>> This is a mischaracterization and you know it.
>>>
>>> -- Gaby
>>
>> It is and it isn't. ?The guy willing to do the basic color stuff has
>> no desire to do what you want. ?Is there someone else lined up to do
>> it? ?If not, then forcing a wait on it effectively blocks the
>> available developer.
>
> No. When you submit a patch to GCC (whether it is diagnostics or not
> is immaterial), you expect that it will get reviewed and recommendations
> will be made about the appropriate way to get it done. ?Just have a look
> at gcc-patches. ?There is no thing new here. ?If the submitter
> refused to follow the recommendations, it is unfair it is being shut down
> or blocked.

Be that as it may, at the end of the day, we won't have color gcc if
you insist on waiting for the better framework.

Unless, of course, you're going to build the better framework.

When you're hungry, sometimes it's better to take an offer of an apple
when you really want an orange, because otherwise you have nothing.


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