Keep chromium checkout up to date in auto roller.

Keep chromium checkout up to date in auto roller.

R=hinoka@google.com

Committed: https://code.google.com/p/v8/source/detail?r=23438

[Michael Achenbach, 2014-08-26 10:51:13]

machenbach@chromium.org changed reviewers:
+ hinoka@chromium.org, jarin@chromium.org

[Michael Achenbach, 2014-08-26 10:51:13]

PTAL

[Ryan Tseng, 2014-08-26 11:43:23]

hinoka@google.com changed reviewers:
+ hinoka@google.com

[Ryan Tseng, 2014-08-26 11:43:23]

lgtm

add bug #?

https://codereview.chromium.org/504443005/diff/1/tools/push-to-trunk/chromium...
File tools/push-to-trunk/chromium_roll.py (right):

https://codereview.chromium.org/504443005/diff/1/tools/push-to-trunk/chromium...
tools/push-to-trunk/chromium_roll.py:1: #!/usr/bin/env python
I feel like this file can be easily rewritten as a recipe.  And you'd get extra
things for free, like expectations and automatic buildbot runnability

[Michael Achenbach, 2014-08-27 09:20:42]

On 2014/08/26 11:43:23, Ryan T. (EMEA time) wrote:
> lgtm
> 
> add bug #?

Hmm, didn't create one for the git-transition clean-ups. I guess this is the
last one out of 5...

>
https://codereview.chromium.org/504443005/diff/1/tools/push-to-trunk/chromium...
> File tools/push-to-trunk/chromium_roll.py (right):
> 
>
https://codereview.chromium.org/504443005/diff/1/tools/push-to-trunk/chromium...
> tools/push-to-trunk/chromium_roll.py:1: #!/usr/bin/env python
> I feel like this file can be easily rewritten as a recipe.  And you'd get
extra
> things for free, like expectations and automatic buildbot runnability

I thought about that. We can talk offline.

[Michael Achenbach, 2014-08-27 09:39:02]

Committed patchset #1 manually as 23438 (tree was closed).