Google Git
Sign in
coral / releases / f01038d48f4784630df11a124ca2d3044e231a96
commitf01038d48f4784630df11a124ca2d3044e231a96[log] [tgz]
authorJune Tate-Gans <jtgans@google.com>Fri Jul 24 17:22:12 2020 -0400
committerJune Tate-Gans <jtgans@google.com>Fri Jul 24 17:22:12 2020 -0400
tree30eb666300193b6de11374c4870d14e1503aae6b
parentcf4bb41ab943306bb2d74453cb4ed41bac67ad9f [diff]
eagle: Update repo manifest for the 5.0 release

We had to regenerate this one because of the lack of README or
recovery.img.

Change-Id: I5be718cf573175fe9d07e2cb5547c157af6066eb
1 file changed
tree: 30eb666300193b6de11374c4870d14e1503aae6b
  1. enterprise/
  2. README.md
README.md

Release Manifests

What is this?

This directory contains the repo manifests used to build a particular Mendel release. Each time an image is made from Jenkins, the resulting manifest snapshot is placed here to allow for reproducing the build on another machine.

How do I use this?

To make an earlier build with these manifests, simply copy the manifest you need out of this tree into your $ROOTDIR/.repo/manifest.xml and call repo sync to bring your tree up to date with those commits.

The general format of the paths are $BOARDNAME/$RELEASENAME-$RELEASEVER.xml, so to find the eagle 5.0 release for enterprise, you'd want to use the enterprise/eagle-5.0.xml release.