Roll clang again |
||
Issue descriptionTracking bug for the next Clang roll. Previous roll: https://crbug.com/857012 (clang r335864).
,
Jul 6
,
Jul 6
I'm not targeting a specific revision. If it's committed when we roll, it will be part of the roll, otherwise it gets in the next one.
,
Jul 6
#3, I see. Thanks.
,
Jul 8
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c14e942936f57cbd743bec29b89aed2b826ee709 commit c14e942936f57cbd743bec29b89aed2b826ee709 Author: Hans Wennborg <hans@chromium.org> Date: Sun Jul 08 20:12:18 2018 Roll clang 335864:336424. Bug: 860622 Change-Id: I65df098eb78e2a35bec62877c201f81c79eb3bd9 Reviewed-on: https://chromium-review.googlesource.com/1127663 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#573192} [modify] https://crrev.com/c14e942936f57cbd743bec29b89aed2b826ee709/tools/clang/scripts/update.py
,
Jul 13
Yes, this is fixed, so removing that blocker again. Next roll is issue 863425 , added it there. |
||
►
Sign in to add a comment |
||
Comment 1 by h...@chromium.org
, Jul 6