Issue 4842043: Move syzygy binary release to public repo.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
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
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
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
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 4842043: Move syzygy binary release to public repo. (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
12 years, 8 months ago by Roger McFarlane

Modified:
12 years, 8 months ago

Reviewers:
chrisha, M-A, jeffbailey, Siggi

CC:
sawbuck-changes_googlegroups.com

Base URL:
http://sawbuck.googlecode.com/svn/trunk/

Visibility:
Public.

Description

Move syzygy binary release to public repo. Committed: http://code.google.com/p/sawbuck/source/browse/#svn/trunk392

Patch Set 1 #

Created: 12 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+76 lines, -0 lines)			Patch
A	syzygy/binaries/Benchmark_Chrome-0.1_r380-py2.6.egg	View	Binary file		0 comments	Download
A	syzygy/binaries/ETW-0.6.5.0-py2.6.egg	View	Binary file		0 comments	Download
A	syzygy/binaries/ETW_Db-0.1_r365-py2.6.egg	View	Binary file		0 comments	Download
A	syzygy/binaries/benchmark.bat	View	1 chunk	+38 lines, -0 lines	0 comments	Download
A	syzygy/binaries/optimize.bat	View	1 chunk	+38 lines, -0 lines	0 comments	Download
A	syzygy/binaries/setuptools-0.6c11-py2.6.egg	View	Binary file		0 comments	Download

Messages

Total messages: 4

Expand All Messages | Collapse All Messages

M-A

I feel like the binaries shouldn't be intermixed with the source tree, e.g. it should ...

12 years, 8 months ago (2011-08-02 17:14:43 UTC) #2

Siggi

12 years, 8 months ago (2011-08-02 17:32:37 UTC) #4

I think there'd be a strong argument for doing this if we had a per-project
DEPS file, as then we could avoid syncing the binary release dir when
working on sources.
As-is, everyone syncs /trunk/, so there's not much benefit. I'd like to move
Syzygy to a different repo eventually, at which point we should revisit
this.

On Tue, Aug 2, 2011 at 1:14 PM, <maruel@chromium.org> wrote:

> I feel like the binaries shouldn't be intermixed with the source tree,
> e.g. it should be in a directory directly under /trunk/.
>
> I don't have a strong opinion.
>
>
>
http://codereview.appspot.com/**4842043/<http://codereview.appspot.com/4842043/>
>

Expand All Messages | Collapse All Messages