Directly modify version file on trunk branch in push-to-trunk.

Directly modify version file on trunk branch in push-to-trunk.

- This also shifts the push revision by one to prepare for the deprecation of the prepare push commit
- The version increment is still based on the bleeding_edge version.cc. This will be changed in a follow up CL.

BUG=
R=jkummerow@chromium.org

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

[Michael Achenbach, 2014-03-18 15:18:48]

PTAL

[Jakob Kummerow, 2014-03-19 10:24:08]

LGTM

https://codereview.chromium.org/200763013/diff/1/tools/push-to-trunk/push_to_...
File tools/push-to-trunk/push_to_trunk.py (left):

https://codereview.chromium.org/200763013/diff/1/tools/push-to-trunk/push_to_...
tools/push-to-trunk/push_to_trunk.py:341: self.GitAdd(self.Config(VERSION_FILE))
Are you sure we don't need this anymore, having just modified the file? Even if
it was staged for commit before, I think the modifications have to be staged
explicitly again.

[Michael Achenbach, 2014-03-19 10:43:33]

On 2014/03/19 10:24:08, Jakob wrote:
> LGTM
> 
>
https://codereview.chromium.org/200763013/diff/1/tools/push-to-trunk/push_to_...
> File tools/push-to-trunk/push_to_trunk.py (left):
> 
>
https://codereview.chromium.org/200763013/diff/1/tools/push-to-trunk/push_to_...
> tools/push-to-trunk/push_to_trunk.py:341:
self.GitAdd(self.Config(VERSION_FILE))
> Are you sure we don't need this anymore, having just modified the file? Even
if
> it was staged for commit before, I think the modifications have to be staged
> explicitly again.

The following commit includes the -a option. Therefore it also works for the
ChangeLog file that is modified in a similar way.

[Michael Achenbach, 2014-03-19 10:46:31]

Committed patchset #1 manually as r20054 (presubmit successful).