Issue 201633002: Fix maintaining change log 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 201633002: Fix maintaining change log in push-to-trunk. (Closed)

Created:
6 years, 9 months ago by Michael Achenbach

Modified:
6 years, 9 months ago

Reviewers:
Jarin

CC:
v8-dev, Jakob Kummerow

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

Visibility:
Public.

Fix maintaining change log in push-to-trunk. Applying the patch on ChangeLog causes local changes. To reset the ChangeLog to its original state, the "-f" option is required. TBR=jarin@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=19963

Created: 6 years, 9 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -2 lines)			Patch
	M	tools/push-to-trunk/git_recipes.py	View		1 chunk	+1 line, -1 line	0 comments	Download
	M	tools/push-to-trunk/test_scripts.py	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 2 (0 generated)

Michael Achenbach

6 years, 9 months ago (2014-03-17 08:51:33 UTC) #2

Message was sent while issue was closed.

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