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
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 when I
status-firefox41: affected
https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41list_id=12290852o1=anyexactquery_format=advancedf2=OPv1=affectedproduct=SeaMonkey
Why are these SeaMonkey bugs flagged status-firefox40: affected
https://bugzilla.mozilla.org/buglist.cgi?f1
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 philip.c...@gmail.com wrote:
Why are these SeaMonkey bugs flagged status-firefox41: affected
https
Why are these SeaMonkey bugs flagged status-firefox41: affected
https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41list_id=12290852o1=anyexactquery_format=advancedf2=OPv1=affectedproduct=SeaMonkey
Why are these SeaMonkey bugs flagged status-firefox40: affected
https
5 matches
Mail list logo