Mike Stump wrote:
> On Jan 11, 2007, at 10:47 PM, Joe Buck wrote:
>> The description of WORKSFORME sounds closest: we don't know how to
>> reproduce the bug. Should that be used?
>
> No, not generally.
Of the states we have, WORKSFORME seems best to me, and I agree with Joe
that there's benefit
On Jan 11, 2007, at 10:47 PM, Joe Buck wrote:
The description of WORKSFORME sounds closest: we don't know how to
reproduce the bug. Should that be used?
No, not generally. This should only be used if someone says, I
compile foo on platform bar and it didn't build and then someone
tries bu
On Fri, Jan 12, 2007 at 12:41:08PM +0100, Eric Botcazou wrote:
> > > Saddest is that is that in a batch of various related bug closings, the
> > > blanket comment "M68k/ColdFire is not a primary platform - CLOSED".
> >
> > That should not happen, they should only get their target milestone
> > bump
> > Saddest is that is that in a batch of various related bug closings, the
> > blanket comment "M68k/ColdFire is not a primary platform - CLOSED".
>
> That should not happen, they should only get their target milestone
> bumped. I cannot remember having seen any case of a bug being _closed_
> jus
Peter Barada <[EMAIL PROTECTED]> writes:
> Saddest is that is that in a batch of various related bug closings, the
> blanket comment "M68k/ColdFire is not a primary platform - CLOSED".
That should not happen, they should only get their target milestone
bumped. I cannot remember having seen any c
> The description of WORKSFORME sounds closest: we don't know how to
> reproduce the bug. Should that be used? The only other choices
> are FIXED (wrong), DUPLICATE (wrong), INVALID (we don't know that),
> or WONTFIX (we're not saying we won't fix it if we get a testcase).
>
> This came up beca
