Manually roll blink into chromium.

Manually roll blink into chromium.

The ARB needs updating to use git commit numbers rather than SVN revisions so trying to manually change DEPS.

BUG=
TBR=gavinp

Committed: https://crrev.com/fca0f33a4923b0cd3ee4c18e33416baa941ddecb
Cr-Commit-Position: refs/heads/master@{#291691}

[wibling-chromium, 2014-08-25 14:22:16]

The CQ bit was checked by wibling@chromium.org

[commit-bot: I haz the power, 2014-08-25 14:22:48]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/wibling@chromium.org/487363005/1

[commit-bot: I haz the power, 2014-08-25 15:35:20]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[commit-bot: I haz the power, 2014-08-25 16:16:08]

Committed patchset #1 (1) as da2ff2c3983c688db1f1bb54b4f7092d00d8d85e

[Jeffrey Yasskin, 2014-08-25 23:23:01]

jyasskin@chromium.org changed reviewers:
+ jyasskin@chromium.org

[Jeffrey Yasskin, 2014-08-25 23:23:01]

What blink revision numbers did this roll into Chromium?

[chromium-reviews, 2014-08-26 06:57:17]

f0e57d49d0f3a0e43e0db29852ef9779a98505bd corresponds to r180846 in the old
world.

If you do git log and search for f0e57d49d0f3a0e43e0db29852ef9779a98505bd
you can find the commit and the old revision number.


On Tue, Aug 26, 2014 at 1:23 AM, <jyasskin@chromium.org> wrote:

> What blink revision numbers did this roll into Chromium?
>
> https://codereview.chromium.org/487363005/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[ccameron, 2014-09-02 20:51:12]

Please always provide a link to view the revisions being rolled.

[commit-bot: I haz the power, 2014-09-10 02:34:50]

Patchset 1 (id:??) landed as
https://crrev.com/fca0f33a4923b0cd3ee4c18e33416baa941ddecb
Cr-Commit-Position: refs/heads/master@{#291691}