Closed
Bug 1506177
Opened 6 years ago
Closed 6 years ago
layout/style/ns*List.h: do not format
Categories
(Developer Infrastructure :: Lint and Formatting, defect)
Developer Infrastructure
Lint and Formatting
Tracking
(firefox-esr60 fixed, firefox65 fixed)
RESOLVED
FIXED
mozilla65
People
(Reporter: Sylvestre, Assigned: Sylvestre)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
lizzard
:
approval-mozilla-esr60+
|
Details |
Ignore more stuff
|
Assignee | |
Comment 1•6 years ago
|
||
Pushed by sledru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a1caf63b7682
Ignore the formating on all layout/style/ns*List.h file r=emilio
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
|
||
Comment 4•6 years ago
|
||
Comment on attachment 9024015 [details]
Bug 1506177 - Ignore the formating on all layout/style/ns*List.h file r?emilio
[ESR Uplift Approval Request]
If this is not a sec:{high,crit} bug, please state case for ESR consideration: This is required for easier backporting of patches after the reformatting of ESR using clang-format.
User impact if declined: Declining this will negatively impact our developers' ability to easily backport their patches to ESR in the future.
Fix Landed on Version: 65
Risk to taking this patch: Low
Why is the change risky/not risky? (and alternatives if risky): NPOTB
String or UUID changes made by this patch: None
Attachment #9024015 -
Flags: approval-mozilla-esr60?
status-firefox-esr60:
--- → affected
Comment on attachment 9024015 [details]
Bug 1506177 - Ignore the formating on all layout/style/ns*List.h file r?emilio
OK for uplift to ESR60 as part of the clang-format project.
Attachment #9024015 -
Flags: approval-mozilla-esr60? → approval-mozilla-esr60+
|
|
||
Comment 6•6 years ago
|
||
| bugherder uplift | ||
|
||
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•