Issue 223093003: Add version number to commit message in merge-to-branch.

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 223093003: Add version number to commit message in merge-to-branch. (Closed)

Created:
6 years, 8 months ago by Michael Achenbach

Modified:
6 years, 8 months ago

Reviewers:
Jarin

CC:
v8-dev, Jakob Kummerow

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

Visibility:
Public.

More Reviews

Description

Add version number to commit message in merge-to-branch. This is a step towards automatically rolling arbitrary trunk revisions into Chromium. This also deprecates the bash scripts as they now start to divert. BUG= R=jarin@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=20465

Patch Set 1 #

Created: 6 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+12 lines, -547 lines)			Patch
D	tools/common-includes.sh	View	1 chunk	+0 lines, -198 lines	0 comments	Download
D	tools/merge-to-branch.sh	View	1 chunk	+0 lines, -342 lines	0 comments	Download
M	tools/push-to-trunk/merge_to_branch.py	View	4 chunks	+9 lines, -6 lines	0 comments	Download
M	tools/push-to-trunk/test_scripts.py	View	1 chunk	+3 lines, -1 line	0 comments	Download

Messages

Total messages: 3 (0 generated)

Expand Messages | Collapse Messages

Michael Achenbach

6 years, 8 months ago (2014-04-03 09:42:32 UTC) #3

Message was sent while issue was closed.

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

Expand Messages | Collapse Messages