Issue 203773013: Retrieve current version from trunk branch in push-to-trunk.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 203773013: Retrieve current version from trunk branch in push-to-trunk. (Closed)

Created:
6 years, 9 months ago by Michael Achenbach

Modified:
6 years, 9 months ago

Reviewers:
Jakob Kummerow

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Visibility:
Public.

More Reviews

Description

Retrieve current version from trunk branch in push-to-trunk. - This moves retrieving and incrementing the version before creating the change log - Before the prepare push commit will be deprecated (follow up CL), the script deals with 3 build levels. X: the current build level on the last trunk push. X + 1: the build level for this trunk push. X + 2: the build level of the new version file on bleeding edge (to be deprecated). BUG= R=jkummerow@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=20071

Patch Set 1 #

Created: 6 years, 9 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+66 lines, -49 lines)			Patch
M	tools/push-to-trunk/git_recipes.py	View	1 chunk	+3 lines, -3 lines	0 comments	Download
M	tools/push-to-trunk/push_to_trunk.py	View	5 chunks	+45 lines, -35 lines	0 comments	Download
M	tools/push-to-trunk/test_scripts.py	View	9 chunks	+18 lines, -11 lines	0 comments	Download

Messages

Total messages: 3 (0 generated)

Expand Messages | Collapse Messages

Michael Achenbach

6 years, 9 months ago (2014-03-19 13:10:50 UTC) #3

Message was sent while issue was closed.

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

Expand Messages | Collapse Messages