Sounds like you need to fork the whole branch then do a revert to that
commit , then build the project.
Or
Since is just the BT, goto that folder before you build and do a revert for
that file , compile just that portion of the project, and import that
intonyour device to see if that works.
Just mu
That change likely arrived in AOSP as part of the lollipop release drop, so
there are no more fine-grained builds available.
On Mon, Jul 1, 2019 at 8:05 AM Alex wrote:
> This idea is great but it works only if the project has been built by the
> CI with head the targeted commit.
> However, in mo
This idea is great but it works only if the project has been built by the
CI with head the targeted commit.
However, in most cases the CI did not build every changes (I'm looking at a
commit from 2015)
For example:
Project: frameworks/av
CommitId: aa4da6fa7ca2454f0713de0a5a583b5b8160166
The com
You can download the manifest_*.xml file from any build from the date that
you want, then use repo sync -m /tmp/manifest_*.xml to sync the revisions
from that manifest.
On Fri, Jun 28, 2019 at 7:56 AM Alex wrote:
> Hi folks,
>
> I did not find any related post to my question so I decided to crea
Hi folks,
I did not find any related post to my question so I decided to create one.
However, feel free to link any relevant post I may have missed.
Problem: I would like to build one project in AOSP at a very specific
commit.
The procedure:
- Find the commit ID
- Find the appropriate m
