ish: Trim down the release branchstabilize-wristpin-14469.59.B-ishstabilize-voshyr-14637.B-ishstabilize-quickfix-14695.187.B-ishstabilize-quickfix-14695.124.B-ishstabilize-quickfix-14526.91.B-ishstabilize-14695.85.B-ishstabilize-14695.107.B-ishstabilize-14682.B-ishstabilize-14633.B-ishstabilize-14616.B-ishstabilize-14589.B-ishstabilize-14588.98.B-ishstabilize-14588.14.B-ishstabilize-14588.123.B-ishstabilize-14536.B-ishstabilize-14532.B-ishstabilize-14528.B-ishstabilize-14526.89.B-ishstabilize-14526.84.B-ishstabilize-14526.73.B-ishstabilize-14526.67.B-ishstabilize-14526.57.B-ishstabilize-14498.B-ishstabilize-14496.B-ishstabilize-14477.B-ishstabilize-14469.9.B-ishstabilize-14469.8.B-ishstabilize-14469.58.B-ishstabilize-14469.41.B-ishstabilize-14442.B-ishstabilize-14438.B-ishstabilize-14411.B-ishstabilize-14396.B-ishstabilize-14395.B-ishstabilize-14388.62.B-ishstabilize-14388.61.B-ishstabilize-14388.52.B-ishstabilize-14385.B-ishstabilize-14345.B-ishstabilize-14336.B-ishstabilize-14333.B-ishrelease-R99-14469.B-ishrelease-R98-14388.B-ishrelease-R102-14695.B-ishrelease-R101-14588.B-ishrelease-R100-14526.B-ishfirmware-cherry-14454.B-ishfirmware-brya-14505.B-ishfirmware-brya-14505.71.B-ishfactory-kukui-14374.B-ishfactory-guybrush-14600.B-ishfactory-cherry-14455.B-ishfactory-brya-14517.B-ish

In the interest of making long-term branch maintenance incur as little
technical debt on us as possible, we should not maintain any files on
the branch we are not actually using.

This has the added effect of making it extremely clear when merging CLs
from the main branch when changes have the possibility to affect us.

The follow-on CL adds a convenience script to actually pull updates from
the main branch and generate a CL for the update.

BUG=b:204206272
BRANCH=ish
TEST=make BOARD=arcada_ish && make BOARD=drallion_ish

Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>

1 files changed, 0 insertions, 125 deletions

diff --git a/docs/getting_started_quickly.md b/docs/getting_started_quickly.md
deleted file mode 100644
index 325bef39b0..0000000000
--- a/docs/getting_started_quickly.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Get Started Building EC Images (Quickly)
-
-[TOC]
-
-The
-[Chromium OS Developer Guide](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md)
-and [README](../README.md) walk through the steps needed to fetch and build
-Chromium OS source. These steps can be followed to retrieve and build EC source
-as well. On the other hand, if your sole interest is building an EC image, the
-general developer guide contains some extra unneeded steps.
-
-The fastest possible way to build an EC image is to skip the Chromium OS chroot
-install entirely. The following steps have been tested on an Ubuntu 15.10 (Wily
-Werewolf) 64-bit host machine. Other distros / versions may be used, but
-toolchain incompatibilities may require extra debug.
-
-## Building
-
-1.  Install build / dev tools:
-
-    ```bash
-    sudo apt-get install git libftdi-dev libusb-dev libncurses5-dev gcc-arm-none-eabi
-    ```
-
-1.  Sync the cros-ec git repo:
-
-    ```bash
-    git clone https://chromium.googlesource.com/chromiumos/platform/ec
-    ```
-
-1.  Build your EC image:
-
-    ```bash
-    HOSTCC=x86_64-linux-gnu-gcc CROSS_COMPILE_arm=arm-none-eabi- make BOARD=${BOARD}
-    ```
-
-    Note: the EC supports multiple architectures, check `core/*/build.mk` files
-    for other supported `CROSS_COMPILE_` variables.
-
-## External Dependencies
-
-Most boards are buildable, but some will fail due to dependencies on external
-binaries (such as [`futility`](#building-futility)). Also, some related tools
-(such as `flash_ec` and `servod`) must be run from the Chromium OS chroot. Here
-is a set of steps to setup a minimal development environment to build EC images
-from the Chromium OS chroot:
-
-1.  Create a folder for your chroot:
-
-    ```bash
-    mkdir cros-src; cd cros-src
-    ```
-
-1.  Run
-
-    ```bash
-    repo init -u https://chromium.googlesource.com/chromiumos/manifest -g minilayout,firmware
-    ```
-
-1.  Run `repo sync`:
-
-    ```bash
-    repo sync -j <number of cores on your workstatsion>
-    ```
-
-1.  Enter the chroot and enter your password for `sudo` if prompted:
-
-    ```bash
-    ./chromite/bin/cros_sdk
-    ```
-
-1.  Set up your board:
-
-    ```bash
-    setup_board --board=${BOARD}
-    ```
-
-    (ex. `setup_board --board=glados`)
-
-1.  Build EC:
-
-    ```bash
-    ./build_packages --board=${BOARD} chromeos-ec
-    ```
-
-1.  Now, EC images for any board can be built with:
-
-    ```bash
-    cd ~/trunk/src/platform/ec; make BOARD=${BOARD} -j
-    ```
-
-## Building `futility` outside the chroot {#building-futility}
-
-If you want to build the `futility` host tool outside the normal Chrome OS
-chroot self-contained environment, you can try the following
-
-1.  Install futility build dependencies:
-
-    ```bash
-    sudo apt-get install uuid-dev liblzma-dev libyaml-dev libssl-dev
-    ```
-
-1.  Get the vboot reference sources:
-
-    ```bash
-    git clone https://chromium.googlesource.com/chromiumos/platform/vboot_reference
-    ```
-
-1.  Build it:
-
-    ```bash
-    cd vboot_reference ; make
-    ```
-
-1.  Install it in `/usr/local/bin`:
-
-    ```bash
-    sudo make install
-    ```
-
-1.  Add `/usr/local/bin` to your default `PATH`:
-
-    ```bash
-    export PATH="${PATH}:/usr/local/bin"
-    ```