Let v8 standalone builds use update.py instead of update.sh.

Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n

Committed: https://crrev.com/39bef217a39cc097cf6057a9a9706aa440f75cfe
Cr-Commit-Position: refs/heads/master@{#32529}

[Nico, 2015-12-02 18:35:16]

thakis@chromium.org changed reviewers:
+ machenbach@chromium.org

[Nico, 2015-12-02 18:36:04]

Description was changed from

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

BUG=chromium:494442
==========

to

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

BUG=chromium:494442
LOG=n
==========

[Nico, 2015-12-02 18:45:08]

Description was changed from

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

BUG=chromium:494442
LOG=n
==========

to

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n
==========

[Michael Achenbach, 2015-12-02 20:11:22]

lgtm

[Nico, 2015-12-02 20:11:42]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-12-02 20:11:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1495653002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1495653002/20001

[commit-bot: I haz the power, 2015-12-02 20:25:49]

Description was changed from

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n
==========

to

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n
==========

[commit-bot: I haz the power, 2015-12-02 20:25:49]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-12-02 20:28:23]

Description was changed from

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n
==========

to

==========
Let v8 standalone builds use update.py instead of update.sh.

update.sh is gone in chromium, and using update.py will do the right
thing both before and after the deletion in chromium (previously,
update.py used to call update.sh internally on non-win).

This also has the benefit of working on Windows.

No intended behavior change.

BUG=chromium:494442
LOG=n

Committed: https://crrev.com/39bef217a39cc097cf6057a9a9706aa440f75cfe
Cr-Commit-Position: refs/heads/master@{#32529}
==========

[commit-bot: I haz the power, 2015-12-02 20:28:23]

Patchset 2 (id:??) landed as
https://crrev.com/39bef217a39cc097cf6057a9a9706aa440f75cfe
Cr-Commit-Position: refs/heads/master@{#32529}