Create a cros directory under client, and start moving things into it.

Create a cros directory under client, and start moving things into it.
The first step only includes chromeos_constants.py. But you get the idea how the others will look like.

Change-Id: I0a601a53e4d9a43f06e9f9f67429ac780f2562d0

BUG=7236
TEST=bvt test

I dont worry too much about occasional break ups caused by this, since I will continues working on this refactoring and this is just the beginning.

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=4b1222e

[truty, 2010-12-06 20:52:56]

I'm not the primary reviewer but I reviewed this anyway.  I'd point out that
Eric also does some cleanup of removing the constants import when it's unused. 
LGTM.

[kmixter1, 2010-12-06 23:20:07]

Didn't look at every file, but assuming that the only change is moving
chromeos_constants to cros/constants.py LGTM.  Assuming also that you'll be
moving more files over there in short order so that people adding new
chromeos-specific modules know exactly where they should go (cros subdir).

[ericli, 2010-12-06 23:23:20]

Yes, I will landing a bunch of changes and every change will only move a
small set of files.

Thanks, I will push shortly.

On Mon, Dec 6, 2010 at 3:20 PM, <kmixter@chromium.org> wrote:

> Didn't look at every file, but assuming that the only change is moving
> chromeos_constants to cros/constants.py LGTM.  Assuming also that you'll be
> moving more files over there in short order so that people adding new
> chromeos-specific modules know exactly where they should go (cros subdir).
>
>
> http://codereview.chromium.org/5519008/
>



-- 
Eric Li
李咏竹
Google Kirkland