Issue 2571413002: [Merge M-56] Updating the CLD3 commit hash in DEPS

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 2571413002: [Merge M-56] Updating the CLD3 commit hash in DEPS (Closed)

Created:
4 years ago by please use gerrit instead

Modified:
4 years ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/pending/branch-heads/2924

Project:
chromium

Visibility:
Public.

[Merge M-56] Updating the CLD3 commit hash in DEPS The main changes are: 1) a retrained model with additional script-based features. GitHub page showing the diff: https://github.com/google/cld3/commit/fa5974a4d3b5e7934fcb166ff26ed6bfce68b18a 2) updating the feature spec parser to parse features without args. GitHub page showing the diff: https://github.com/google/cld3/commit/c03368eff92acc56756df2d4cd74a01a674409ea BUG=672185 Review-Url: https://codereview.chromium.org/2560473004 Cr-Commit-Position: refs/heads/master@{#437081} (cherry picked from commit 3382ba03f380d3f681a84c8c8bf83bebf9ca2b7c) Committed: https://chromium.googlesource.com/chromium/src/+/0263b027555a01ea660cf77eaffdac9981d923bb

Created: 4 years ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	DEPS	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 2 (1 generated)

please use gerrit instead

4 years ago (2016-12-14 22:02:25 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
0263b027555a01ea660cf77eaffdac9981d923bb.