Duplicate radars: good or bad? (Was: Re: Building 10.6' ld64)
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Sep 4, 2009, at 10:00 AM, William Siegrist wrote: For example: On Oct 29, 2007, at 6:15 PM, Chris Espinosa wrote: On Oct 29, 2007, at 5:10 PM, David Catmull wrote: Don't let a resolution of "duplicate" keep you from filing bugs. -- Steve Checkoway _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... The Darwin Team is aware of the request for libunwind. I'll put down another vote for it, so no need to file more radars or emails. Comments like this confuse me since other @apple.com people have said that radars are the only way Apple knows what people are wanting and duplicate radars show more interest. On Oct 29, 2007, at 4:28 PM, Chris Hanson <cmh@mac.com> wrote: It ought to be just the opposite: it means you're not the only one complaining about the issue, which should be encouraging. It is, in fact. Many teams (mine included) put a premium on high- dup-count bugs, and the Mac OS X Project Office usually gives recognition and a small prize for the engineer who fixed the bug with higest dup count in a given release. This email sent to site_archiver@lists.apple.com
participants (1)
-
Steve Checkoway