public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: "Jakub Jelinek" <jakub@redhat.com>,
	"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
	"Ian Lance Taylor" <iant@google.com>,
	"Lawrence Crowl" <crowl@google.com>,
	"Jonathan Wakely" <jwakely.gcc@gmail.com>,
	"gcc Mailing List" <gcc@gcc.gnu.org>
Subject: Re: Updated GCC vs Clang diagnostics
Date: Fri, 13 Apr 2012 15:59:00 -0000	[thread overview]
Message-ID: <CAF1jjLsU1X4nnL8DG_1AWi-5zz70TvVg0WQEbXGmONcssDovKg@mail.gmail.com> (raw)
In-Reply-To: <CAAiZkiDNfuNXX+1ZCKC4viGc1Y2JNAoZ+4spATdQ4xsCM-OWJg@mail.gmail.com>

On Fri, Apr 13, 2012 at 11:53 AM, Gabriel Dos Reis
<gdr@integrable-solutions.net> wrote:
> On Fri, Apr 13, 2012 at 10:41 AM, NightStrike <nightstrike@gmail.com> wrote:
>> 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.
>
> Not necessarily.
>
> Would you or Jakub say that he is attempting to shoot down the switch to C++,
> just  because he wants to see some components converted done first
> (blue sky redesigned done first) even though he did not explicitly offer to
> do that conversion himself, or would  you say that he is making a
> recommendation
> of what he considers to be in  the best long term interest. I would
> say the latter.
> Orange and apple analogy aside.
>
>
> -- Gaby

Ok, fine, but then explain to me how color gcc happens if nobody wants
to do the extra work you want?

  reply	other threads:[~2012-04-13 15:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 21:50 Manuel López-Ibáñez
2012-04-12 21:54 ` Gabriel Dos Reis
2012-04-12 22:05   ` Manuel López-Ibáñez
2012-04-12 22:18     ` Lawrence Crowl
2012-04-13  5:12       ` Ian Lance Taylor
2012-04-13  5:58         ` Gabriel Dos Reis
2012-04-13  6:03         ` Jakub Jelinek
2012-04-13  6:07           ` Gabriel Dos Reis
2012-04-13  8:41           ` Manuel López-Ibáñez
2012-04-13  8:47             ` Gabriel Dos Reis
2012-04-13  9:00               ` Manuel López-Ibáñez
2012-04-13  9:09                 ` Gabriel Dos Reis
2012-04-13 14:23                   ` Jakub Jelinek
2012-04-13 15:23                     ` Gabriel Dos Reis
2012-04-13 15:30                       ` NightStrike
2012-04-13 15:36                         ` Gabriel Dos Reis
2012-04-13 15:41                           ` NightStrike
2012-04-13 15:53                             ` Gabriel Dos Reis
2012-04-13 15:59                               ` NightStrike [this message]
2012-04-13 16:02                                 ` Gabriel Dos Reis
2012-04-13 20:59         ` Lawrence Crowl
2012-04-14  6:58           ` Marc Glisse
2012-04-12 22:18     ` Gabriel Dos Reis
2012-04-12 22:43       ` Manuel López-Ibáñez
2012-04-13  1:40         ` Joe Buck
2012-04-13  2:27           ` Manuel López-Ibáñez
2012-04-13  3:37             ` Gabriel Dos Reis
2012-04-13  8:27               ` Manuel López-Ibáñez
2012-04-13  8:41                 ` Gabriel Dos Reis
2012-04-13  9:08                 ` Jonathan Wakely
2012-04-13  8:59           ` Jonathan Wakely
2012-04-13  9:04             ` Gabriel Dos Reis
2012-04-13 10:54               ` Manuel López-Ibáñez
2012-04-13 11:36                 ` Richard Guenther
2012-04-13 13:40                   ` Gabriel Dos Reis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF1jjLsU1X4nnL8DG_1AWi-5zz70TvVg0WQEbXGmONcssDovKg@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=crowl@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=iant@google.com \
    --cc=jakub@redhat.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=lopezibanez@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).