On 01/06/2015 12:18, glob wrote:
> this started happening via
> https://bugzilla.mozilla.org/show_bug.cgi?id=972040
>
> please file a bug and we'll apply per-product filtering -- currently
> it'll be set on any product that has that flag.
I have filed https://bugzilla.mozilla.org/show_bug.cgi?i
this started happening via
https://bugzilla.mozilla.org/show_bug.cgi?id=972040
please file a bug and we'll apply per-product filtering -- currently
it'll be set on any product that has that flag.
(i'm not sure why seamonkey has that flag visible on its bugs)
-glob
Philip Chee wrote:
On 31
On 31/05/2015 16:02, Sylvestre Ledru wrote:
> I don't know about this specific issue but I asked to Ryan a few
> months back that the status firefox would be automatically marked as
> "fixed" for the current nightly. I guess this is related to this.
Yahbutt the flag doesn't get changed to fixed wh
e:
>
>> Why are these SeaMonkey bugs flagged status-firefox41: affected
>>
>> https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey
>>
>> Why a
Bugzilla has defaulted to marking new bugs as status-firefoxXX: affected.
I'm not sure when it started but this is why.
Hope that helps,
Jared
On Sat, May 30, 2015 at 11:58 AM, Philip Chee wrote:
> Why are these SeaMonkey bugs flagged status-firefox41: affected
>
> https://bugzil
Why are these SeaMonkey bugs flagged status-firefox41: affected
https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey
Why are these SeaMonkey bugs flagged status-f
6 matches
Mail list logo