On Thu, Jul 31, 2014 at 04:01:48PM -0000, JaSauders wrote:
> There was a lengthy bug report that was just split off to a new report
> to centralize around these issues. Perhaps you can read it over and see
> if this applies to you.
No!
I've been trying to be clear in my previous responses to your messages,
but let me reiterate: I do _not_ want a centralized bug report. It's
better for users to file an individual bug report so we can capture the
logs and hardware information from that machine, unless they have the
exact same machine and symptoms as the existing bug. We can always dup
bugs later if we find out that they really do represent the same
problem.
In this case the problems are clearly unrelated, since this one is about
a firmware crash and the one you point out has nothing to do with
firmware crashes. When we start piling unrelated problems onto a single
bug report it can quickly become unmanagable. So _please_ do not point
people at a single, "central" bug report for 7260 wireless issues.
Thanks!
On Thu, Jul 31, 2014 at 04:01:48PM -0000, JaSauders wrote:
> There was a lengthy bug report that was just split off to a new report
> to centralize around these issues. Perhaps you can read it over and see
> if this applies to you.
No!
I've been trying to be clear in my previous responses to your messages,
but let me reiterate: I do _not_ want a centralized bug report. It's
better for users to file an individual bug report so we can capture the
logs and hardware information from that machine, unless they have the
exact same machine and symptoms as the existing bug. We can always dup
bugs later if we find out that they really do represent the same
problem.
In this case the problems are clearly unrelated, since this one is about
a firmware crash and the one you point out has nothing to do with
firmware crashes. When we start piling unrelated problems onto a single
bug report it can quickly become unmanagable. So _please_ do not point
people at a single, "central" bug report for 7260 wireless issues.
Thanks!