From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>,
gcc@gcc.gnu.org, Ian Lance Taylor <iant@google.com>
Subject: Re: PowerPC suboptimal "add with carry" optimization
Date: Mon, 26 Apr 2010 15:11:00 -0000 [thread overview]
Message-ID: <l2p84144f021004260733h5eaa7baaned11497e1b763f33@mail.gmail.com> (raw)
In-Reply-To: <z2o6c33472e1004260627vb76ef24ey1c72ec43231639dc@mail.gmail.com>
Hi Manuel,
On Mon, Apr 26, 2010 at 4:27 PM, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
>> I guess that's the point, really. 15 minutes for what exactly? All the
>> information is right there in the email Joakim sent. You are trying to
>> make life easier for developers, not users or testers.
>
> I think you misunderstood the thread then. More users and more testers
> would be nice but we really need more developers (or people
> contributing documentation, infrastructure support, etc). So making
> life easier for developers is contributing. Making life harder for
> developers is not.
I guess the conventional wisdom says that the way to attract new
developers is to first attract users and testers and then turn them
into contributors.
I can understand what you're trying to achieve with your bug tracking
system but I'm questioning if it's working for you. I am looking at
this from Linux kernel development point of view and the lessons
learned there is that the lower you can make the barrier for entry
(bug reports, patches, etc.), the more likely you're going to keep old
people around and attract new ones.
But anyway, I'm not trying to argue with you or force my views on you.
I'm just stating my observation which is extremely biased towards what
I see as a working model (the Linux kernel).
On Mon, Apr 26, 2010 at 4:27 PM, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
> You mention "reality" below. If you really want a particular bug
> fixed, then you should try to help the developers to fix it. Reality
> is that bugs that are not in bugzilla do not get fixed because
> developers prefer to spend their time efficiently on well-structured
> reports and on high impact bugs. So my comment is trying to help you
> to increase the chances that your bug gets fixed. But if yourself
> don't care, then why do you expect others do?
That's something you can change. But trying to convince people that
your bug tracking system is not a pain in the ass isn't going to
change things.
Pekka
next prev parent reply other threads:[~2010-04-26 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 13:05 Joakim Tjernlund
2010-04-25 19:09 ` Ian Lance Taylor
2010-04-26 7:43 ` Joakim Tjernlund
2010-04-26 12:10 ` Manuel López-Ibáñez
2010-04-26 12:23 ` Joakim Tjernlund
2010-04-26 12:42 ` Manuel López-Ibáñez
2010-04-26 12:45 ` Pekka Enberg
2010-04-26 12:54 ` David Edelsohn
2010-04-26 12:55 ` Pekka Enberg
2010-04-26 13:30 ` Manuel López-Ibáñez
2010-04-26 15:11 ` Pekka Enberg [this message]
2010-04-26 15:30 ` Manuel López-Ibáñez
2010-04-26 12:58 ` David Edelsohn
2010-04-26 13:27 ` Joakim Tjernlund
2010-04-26 13:38 ` Manuel López-Ibáñez
2010-04-26 13:42 ` Joakim Tjernlund
2010-04-26 14:01 ` Ian Lance Taylor
2010-04-26 13:57 ` David Edelsohn
2010-04-26 8:04 ` Joakim Tjernlund
2010-04-26 14:15 ` Ian Lance Taylor
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=l2p84144f021004260733h5eaa7baaned11497e1b763f33@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=joakim.tjernlund@transmode.se \
--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).