From 808ea578e1597271a1a73de640e9957babb4f9ea Mon Sep 17 00:00:00 2001 From: "mseaborn@chromium.org" Date: Wed, 1 Sep 2010 16:22:01 +0000 Subject: Pull seccomp-sandbox in via DEPS rather than using an in-tree copy This means changes to the sandbox won't have to be committed twice, to both trees. This is a retry of r57921, which was committed with git-svn and failed to remove the "seccomp" directory. This caused problems when trying to "svn checkout" to the same location, and the change was reverted. This time I will use SVN to commit the change. BUG=none TEST=smoke test of running chromium with --enable-seccomp-sandbox Review URL: http://codereview.chromium.org/3225010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58184 0039d316-1c4b-4281-b951-d872f2087c98 --- DEPS | 3 +++ 1 file changed, 3 insertions(+) (limited to 'DEPS') diff --git a/DEPS b/DEPS index 21c2911..8298c8a 100644 --- a/DEPS +++ b/DEPS @@ -21,6 +21,9 @@ deps = { "src/googleurl": "http://google-url.googlecode.com/svn/trunk@145", + "src/seccompsandbox": + "http://seccompsandbox.googlecode.com/svn/trunk@91", + "src/sdch/open-vcdiff": "http://open-vcdiff.googlecode.com/svn/trunk@28", -- cgit v1.1