Back to bug 39197

Who When What Removed Added
smcv 2011-07-13 09:41:19 UTC Assignee hp simon.mcvittie
Keywords patch
Status NEW ASSIGNED
CC hp, lool, mbiebl, will.thompson
Blocks 36164
smcv 2012-02-07 12:22:03 UTC Attachment #49047 Attachment is obsolete 0 1
smcv 2012-02-07 12:22:43 UTC Attachment #56718 Attachment is obsolete 0 1
Attachment #49048 Attachment is obsolete 0 1
smcv 2012-02-07 12:23:40 UTC Attachment #49049 Attachment is obsolete 0 1
smcv 2012-02-07 12:24:12 UTC Attachment #49050 Attachment is obsolete 0 1
smcv 2012-02-07 12:25:27 UTC Blocks 39196
smcv 2012-06-05 03:56:03 UTC Whiteboard review?
smcv 2012-06-12 04:18:07 UTC Whiteboard review? review+
smcv 2012-06-15 05:39:32 UTC Status ASSIGNED RESOLVED
Resolution --- FIXED
smcv 2012-06-25 13:10:00 UTC Whiteboard review+
Status RESOLVED REOPENED
Resolution FIXED ---
smcv 2012-06-25 13:11:16 UTC Attachment #56722 Attachment is obsolete 0 1
Attachment #49046 Attachment is obsolete 0 1
Attachment #56719 Attachment is obsolete 0 1
Attachment #56720 Attachment is obsolete 0 1
Attachment #56721 Attachment is obsolete 0 1
jan 2012-06-25 13:46:00 UTC CC jan
smcv 2013-06-05 17:37:36 UTC Attachment #63464 Attachment is obsolete 0 1
khadgaray 2013-09-23 06:54:56 UTC CC khadgaray
chengwei.yang.cn 2013-09-23 09:14:00 UTC CC chengwei.yang.cn
msniko14 2014-09-23 13:56:47 UTC Priority medium highest
CC msniko14
Version unspecified 1.5
Resolution --- FIXED
Severity normal critical
Keywords cleanup0407, i18n, janitor, l10n, security
Status REOPENED RESOLVED
smcv 2014-09-23 15:26:36 UTC Priority highest medium
Severity critical normal
Resolution FIXED ---
Keywords cleanup0407, i18n, janitor, l10n, security
Status RESOLVED REOPENED
smcv 2014-09-25 14:59:21 UTC QA Contact johnp dbus
smcv 2016-07-06 19:06:24 UTC Whiteboard review+
smcv 2016-07-25 10:35:21 UTC Depends on 97014
Whiteboard review+ review+, waiting for fd.o git
smcv 2016-07-25 11:46:03 UTC Status REOPENED RESOLVED
Resolution --- FIXED

Back to bug 39197

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.