Don't make assumptions about the formats of build descriptions

Change-Id: Id83a7594e9e1b9b4ffbdbaba695506d8d0d21a46
kernel: do not assume arch is arm

In the kernel.mk file the target architecture is
assumed to be ARM. This may not be true, so
it's changed to use the $(TARGET_ARCH) variable.

Change-Id: Ia9347a44fcfdc40846e1cd6626c4e574bd93b16f
kernel: add support for bzImages

Some boards, like smi, uses bzImage images for the kernel,
so we add the option enabled by BOARD_USES_BZIMAGE in BoardConfig.mk

Change-Id: I40a889de2d1a201cd10721b4005096d067d0be10
For user builds, use a release build id in the description if one exists

Companion change to Ic5913e587400dd38c04aa05de3a7becced77a59e

Change-Id: If5edbf56d567701f96f0ba46af9a90ffa8310c24
envsetup: Fix remote functions to deal with symlinks

merged CM Commit http://review.cyanogenmod.org/#/c/53961

Change-Id: Idf226d9cb79664af597eeca5f1d005eb6518eff0
Allow defining multiple GCC O Levels 2/2

Change-Id: Idac74b61ece0f9fdc35b29188ec4c5191ebfcae2
Rework if statements for GCC Level. [1/2]

Reworked the if statements to give only 2 options, either Os or O3. If neither one of them is selected as an option, it will select the default Optimization Level which is O2.

PS2: Update commit message
PS3: Rebase and ready for merge

Change-Id: I64d5787bc86242fd613eb3931cd9bd46d7f17c49
Signed-off-by: Lokesh Chamane <lokesh.c703@gmail.com>
The GCC Optimization Levels AGAIN [1/2]

So after lurking around, I found out that we didn't set up the GCC Optimization
Levels to the TARGET_linux_mips.mk and I also found out that the Global Cflags
for TARGET_linux-x86.mk uses O2 in by default. Now I added those GCC
Optimization Levels to it but I'm not sure if they work? ¯\_(ツ)_/¯

PS2: Tabs.
PS3: Update the commit message..
PS4: DONE UPDATING THE COMMIT MESSAGE!

Change-Id: Ibd9e0b5580bdd4d9a865741d856486c35ca1f7f6
Signed-off-by: Lokesh Chamane <lokesh.c703@gmail.com>
RepoPick : Add support for git pull

Allow user to git pull patchsets and dependencies.

Change-Id: If3c255d5e704495001829a69e813fa30e4b8ec48
(2/2)Cherry-pick before build (ported from pac-4.4 branch)

This will enable us to specify gerrit commits not yet merged
to be cherry-picked before build starts

PS1: Port to pac-4.4 branch
- Resolve inconsistent JSON responses
- Fix derp
PS2: Fix CM JSON response; update LX cherry-picks
- Fix derp
PS3: Move cherries.sh to vendor/pac
- compensate for leading zero in fetch/ref

Change-Id: Icbf657759bbe06096c6faa05388d560f0ee2ec48
repopick: add LegacyXperia to known gerrit accounts

Change-Id: I301295535c72a90f39c0241c7551f21103e4098c
Merge remote-tracking branch 'pac/cm-10.2' into cm-10.2