• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Browsing Duplicate Bugs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Browsing Duplicate Bugs


  • Subject: Re: Browsing Duplicate Bugs
  • From: Ray Kiddy <email@hidden>
  • Date: Sun, 19 Feb 2012 14:04:07 -0800

On Feb 19, 2012, at 8:36 AM, Brian Barnes wrote:

> There is no bug in Xcode more disturbing to my workflow then #7493248 -- which is that changing tabs changes the left tree.  When I find in multiple files this drives me nuts, or clicking through errors, with the tree in the left pane constantly changing.  So, I submitted a bug report: #9262331.  It was closed as a duplicate of #7493248.  OK, great, other's have put that in.
>
> So, since it hasn't been fixed yet, I watch the bug report to see what's happening.
>
> Problem is, I can't watch the bug report -- mine was closed as a duplicated and you can't look at other bug reports!
>
> Is it possible to open a slight hole so you can at least view bugs closed as duplicates?  For instance (while not in this case) you might have further information to add, or you might just want to see if any engineer has wrote anything (like a workaround or something.)
>
> Of course, this could get fixe and then I wouldn't have to worry about it :)
>
> [>] Brian

This has been a problem for a while. I have had conversations over 10 years ago with Radar people (Radar is bugreport.a.c from inside Apple) and they knew it was lame then. As far as I am concerned, filing a bug is just throwing a dirty sock over the wall. I will spend a few minutes on it, but no more. Maybe it is a new bug, but there are _so many_ bugs hanging out there, millions of them really, that it is pretty sure to be a duplicate.

If Apple wanted us to take the time to characterize the bugs more fully, they would give us access to the bug that our bug is a duplicate of. Al least then we could all see what the work-arounds might be, since work-arounds go to the original bug and no other. If Apple does not want to share the information, why should we waste our time with it?

- ray


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Browsing Duplicate Bugs
      • From: Joar Wingfors <email@hidden>
References: 
 >Browsing Duplicate Bugs (From: Brian Barnes <email@hidden>)

  • Prev by Date: Re: Browsing Duplicate Bugs
  • Next by Date: One-click multi launch?
  • Previous by thread: Re: Browsing Duplicate Bugs
  • Next by thread: Re: Browsing Duplicate Bugs
  • Index(es):
    • Date
    • Thread