RESOLVED FIXED Bug 39196
Rollout changeset 59274 (as requested by dhyatt on #webkit)
https://bugs.webkit.org/show_bug.cgi?id=39196
Summary Rollout changeset 59274 (as requested by dhyatt on #webkit)
Daniel Bates
Reported 2010-05-16 21:44:34 PDT
Not worth the memory use. Rollout as requested by David Hyatt.
Attachments
Patch (73.49 KB, patch)
2010-05-16 21:47 PDT, Daniel Bates
hyatt: review+
Daniel Bates
Comment 1 2010-05-16 21:47:16 PDT
Created attachment 56209 [details] Patch There were two conflict when rolling this out in files: WebCore/rendering/SVGInlineFlowBox.h (conflict due to changes in http://trac.webkit.org/changeset/59589>). WebCore/rendering/RenderBlockLineLayout.cpp (conflict due to changes in <http://trac.webkit.org/changeset/59588>).
Dave Hyatt
Comment 2 2010-05-16 21:48:42 PDT
Comment on attachment 56209 [details] Patch r=me
WebKit Review Bot
Comment 3 2010-05-16 21:48:48 PDT
Attachment 56209 [details] did not pass style-queue: Failed to run "['WebKitTools/Scripts/check-webkit-style', '--no-squash']" exit_code: 1 WebCore/rendering/InlineBox.h:145: More than one command on the same line [whitespace/newline] [4] WebCore/rendering/InlineTextBox.h:99: More than one command on the same line [whitespace/newline] [4] WebCore/rendering/InlineTextBox.cpp:738: One space before end of line comments [whitespace/comments] [5] WebCore/rendering/InlineTextBox.cpp:911: One space before end of line comments [whitespace/comments] [5] WebCore/rendering/InlineTextBox.cpp:930: One line control clauses should not use braces. [whitespace/braces] [4] Total errors found: 5 in 24 files If any of these errors are false positives, please file a bug against check-webkit-style.
Daniel Bates
Comment 4 2010-05-16 21:52:42 PDT
Comment on attachment 56209 [details] Patch Clearing commit-queue flag. Will update change log to reflect revision we are rolling out and its corresponding bug and land manually.
Daniel Bates
Comment 5 2010-05-16 21:59:34 PDT
Committed in change-set 59592 <http://trac.webkit.org/changeset/59592>.
Note You need to log in before you can comment on or make changes to this bug.