[Chrome OS] Move cros deps inside the main chrome repo

[Chrome OS] Move cros deps inside the main chrome repo

Instead of forcing all linux devs to have an acceptable version of git
installed, mitigate the problem of the cros_deps/DEPS file living outside
the main chrome checkout by moving our extra DEPS file inside the main chrome
tree.

Also change our naming convention to be more like that which is in use
elsewhere in the project.

In a week, cros_deps/DEPS will be end-of-lifed.

BUG=None
TEST=None

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=66153

[bradn, 2010-11-15 19:36:55]

LGTM

http://codereview.chromium.org/4970003/diff/1/tools/cros.DEPS/DEPS
File tools/cros.DEPS/DEPS (right):

http://codereview.chromium.org/4970003/diff/1/tools/cros.DEPS/DEPS#newcode7
tools/cros.DEPS/DEPS:7: Var("chromium_git") + "/cros.git@d4465704",
Is that a sufficiently precise git hash, or should we do the whole thing?

[Chris Masone, 2010-11-15 19:38:27]

That is generally considered to be sufficient.  it's standard within the
community, to teh best of my knowledge, and what we've been using so far.

On Mon, Nov 15, 2010 at 11:36 AM, <bradnelson@google.com> wrote:

> LGTM
>
>
> http://codereview.chromium.org/4970003/diff/1/tools/cros.DEPS/DEPS
> File tools/cros.DEPS/DEPS (right):
>
> http://codereview.chromium.org/4970003/diff/1/tools/cros.DEPS/DEPS#newcode7
> tools/cros.DEPS/DEPS:7: Var("chromium_git") + "/cros.git@d4465704",
> Is that a sufficiently precise git hash, or should we do the whole
> thing?
>
>
> http://codereview.chromium.org/4970003/
>