Bug 81322

Summary: MediaStream API (JSEP): Fixing a few nits
Product: WebKit Reporter: Tommy Widenflycht <tommyw>
Component: WebCore Misc.Assignee: Tommy Widenflycht <tommyw>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, harald, ojan, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 80589    
Attachments:
Description Flags
Patch none

Tommy Widenflycht
Reported 2012-03-16 02:21:17 PDT
Addressing the nits from bugs 81206 and 81207.
Attachments
Patch (2.92 KB, patch)
2012-03-16 02:25 PDT, Tommy Widenflycht
no flags
Tommy Widenflycht
Comment 1 2012-03-16 02:25:20 PDT
Adam Barth
Comment 2 2012-03-16 06:45:52 PDT
Comment on attachment 132232 [details] Patch Thanks!
WebKit Review Bot
Comment 3 2012-03-16 07:21:21 PDT
Comment on attachment 132232 [details] Patch Rejecting attachment 132232 [details] from commit-queue. Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '-..." exit_code: 2 Last 500 characters of output: ommit-queue/Source/WebKit/chromium/third_party/snappy/src --revision 37 --non-interactive --force --accept theirs-conflict --ignore-externals' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' 44>At revision 37. ________ running '/usr/bin/python tools/clang/scripts/update.py --mac-only' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' ________ running '/usr/bin/python gyp_webkit' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium' Updating webkit projects from gyp files... Full output: http://queues.webkit.org/results/11961441
Adam Barth
Comment 4 2012-03-16 07:22:59 PDT
Comment on attachment 132232 [details] Patch Looks like an SVN server problem.
WebKit Review Bot
Comment 5 2012-03-16 07:53:18 PDT
Comment on attachment 132232 [details] Patch Clearing flags on attachment: 132232 Committed r111007: <http://trac.webkit.org/changeset/111007>
WebKit Review Bot
Comment 6 2012-03-16 07:53:22 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.