Added option to set ChromeOS version name, track and AU/dev server URLs via environment variables

Added option to set ChromeOS version name, track and AU/dev server URLs via environment variables

Change-Id: I80914aa49e74edf71914aa93f310104210581ffd

BUG=none
TEST=Ran a x86-generic build and tested from USB drive

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

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=72d0b08

[davidjames, 2010-12-14 01:25:23]

Adding djmm as reviewer per discussion with cmasone on IRC.

Change looks good to me but wanted to double check with djmm to see what
mechanism makes sense for customizing these environment variables. I think it's
reasonable to pick up from the build environment but just wanted to sanity check
with you.

[David McMahon, 2010-12-14 01:45:42]

That's a fine way to pass in values to make the versions dynamic at build time. 
Releases will always be stamped with the appropriate versions in this file, of
course.

LGTM

[Liam McLoughlin, 2010-12-14 03:59:48]

Added another change so that these can be set outside of the chroot, realised
this would be useful when setting up the first patch on my own buildbot.

On 2010/12/14 01:45:42, David McMahon wrote:
> That's a fine way to pass in values to make the versions dynamic at build
time. 
> Releases will always be stamped with the appropriate versions in this file, of
> course.
> 
> LGTM

[David McMahon, 2010-12-14 18:53:23]

LGTM

[anush, 2010-12-14 19:12:56]

I think you may have to push it for him after the LGTM, if he doesnt
have commit access.

On Tue, Dec 14, 2010 at 10:53 AM,  <djmm@google.com> wrote:
> LGTM
>
> http://codereview.chromium.org/5760004/
>

[Liam McLoughlin, 2010-12-14 20:38:03]

If you could push this then, that'd be great! :)

[David McMahon, 2010-12-15 20:49:39]

How does one push for someone else?  Is that documented somewhere?  Also,
the file location has changed.

On Tue, Dec 14, 2010 at 12:38 PM, <hexxeh@hexxeh.net> wrote:

> If you could push this then, that'd be great! :)
>
>
> http://codereview.chromium.org/5760004/
>

[sosa, 2010-12-15 20:56:39]

repo start <Some branch name> . # Creates branch
git cl patch <issue number> # apply CL
git cl push -c "First Last <email addy>" # Push change ... but
attribute contributer.

... this is probably documented somewhere in the chromium docs but unsure where.

On Wed, Dec 15, 2010 at 12:49 PM, David McMahon <djmm@google.com> wrote:
>
> How does one push for someone else?  Is that documented somewhere?  Also,
> the file location has changed.
>
> On Tue, Dec 14, 2010 at 12:38 PM, <hexxeh@hexxeh.net> wrote:
>>
>> If you could push this then, that'd be great! :)
>>
>> http://codereview.chromium.org/5760004/
>
>

[anush, 2010-12-15 20:57:04]

Here is the old doc
http://dev.chromium.org/chromium-os/how-tos-and-troubleshooting/gclient-and-g...

I think it needs to be updated and included in the new doc.. basically

1) repo sync && repo start mybranch .
2) git cl patch <codereview_number>
3) build/test
4) git commit --amend -s --author="John Doe <john.doe@somewhere.com>"
    Here you copy paste the commit log from the code review
description into the git message. The -s is to add a signed off by the
committer and the author resets the author as the person submitting
the patch.
5) git cl push -c "$AUTHOR_NAME <$AUTHOR_EMAIL>"

Thanks

On Wed, Dec 15, 2010 at 12:49 PM, David McMahon <djmm@google.com> wrote:
>
> How does one push for someone else?  Is that documented somewhere?  Also,
> the file location has changed.
>
> On Tue, Dec 14, 2010 at 12:38 PM, <hexxeh@hexxeh.net> wrote:
>>
>> If you could push this then, that'd be great! :)
>>
>> http://codereview.chromium.org/5760004/
>
>

[David McMahon, 2010-12-15 21:25:51]

Thanks Chris, Anush.
The change(s) are committed.

On Wed, Dec 15, 2010 at 12:56 PM, Chris Sosa <sosa@chromium.org> wrote:

> repo start <Some branch name> . # Creates branch
> git cl patch <issue number> # apply CL
> git cl push -c "First Last <email addy>" # Push change ... but
> attribute contributer.
>
> ... this is probably documented somewhere in the chromium docs but unsure
> where.
>
> On Wed, Dec 15, 2010 at 12:49 PM, David McMahon <djmm@google.com> wrote:
> >
> > How does one push for someone else?  Is that documented somewhere?  Also,
> > the file location has changed.
> >
> > On Tue, Dec 14, 2010 at 12:38 PM, <hexxeh@hexxeh.net> wrote:
> >>
> >> If you could push this then, that'd be great! :)
> >>
> >> http://codereview.chromium.org/5760004/
> >
> >
>