[Starlingx-discuss] Updating SHA pointers in build system.
Cordoba Malibran, Erich
erich.cordoba.malibran at intel.com
Sun Jun 17 14:13:36 UTC 2018
In preparation to open source, some components of StarlingX were squashed, this causes that the git
history is different now. Therefore, the TIS_BASE_SRCREV variable is broken for several components
as now points to missing commits, causing a broken build.
My question is what to do with these variables, should we:
- Update to a valid commit
- Set the variable value to HEAD
- Remove those variables, not sure if that's possible.
What do you think is the best course of action.
More information about the Starlingx-discuss