Issue 2934063002: Always use milliseconds in the Budget API implementation

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 2934063002: Always use milliseconds in the Budget API implementation (Closed)

Created:
3 years, 6 months ago by Peter Beverloo

Modified:
3 years, 6 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3112

Project:
chromium

Visibility:
Public.

Always use milliseconds in the Budget API implementation BUG=729656 Review-Url: https://codereview.chromium.org/2922203002 Cr-Original-Commit-Position: refs/heads/master@{#477147} Review-Url: https://codereview.chromium.org/2934063002 . Cr-Commit-Position: refs/branch-heads/3112@{#315} Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897} Committed: https://chromium.googlesource.com/chromium/src/+/3b2aad48388c9af18b28d536d1dc4368d877a153

Created: 3 years, 6 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+7 lines, -6 lines)			Patch
M	chrome/browser/budget_service/budget_database.cc	View	2 chunks	+2 lines, -2 lines	0 comments	Download
M	chrome/browser/budget_service/budget_database_unittest.cc	View	2 chunks	+3 lines, -3 lines	0 comments	Download
M	chrome/browser/budget_service/budget_service_impl.cc	View	1 chunk	+2 lines, -1 line	0 comments	Download

Total messages: 2 (1 generated)

Peter Beverloo

3 years, 6 months ago (2017-06-13 12:27:31 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
3b2aad48388c9af18b28d536d1dc4368d877a153.