[Starlingx-discuss] Updating SHA pointers in build system.

Scott Little scott.little at windriver.com
Mon Jun 25 17:16:56 UTC 2018


I had a look at the tools.  A tag should work.

stx-r1-upstream is our tag for the upstream PARENT of the first STX commit?  That's good to know, and yes we should be consistent across all upstream gits.



On 18-06-18 01:29 PM, Dean Troyer wrote:
> On Mon, Jun 18, 2018 at 11:09 AM, Cordoba Malibran, Erich
> <erich.cordoba.malibran at intel.com> wrote:
>> Ok, I'll update the missing references on these components.
>>
>> ceph/centos/build_srpm.data
>> devtools/qemu/centos/build_srpm.data
>> openstack/openstack-ras/centos/build_srpm.data
>> openstack/python-ceilometerclient/centos/build_srpm.data
>> openstack/python-openstacksdk/centos/build_srpms.data
> Ah, they are all upstream repos on github.  We could tag the squash
> commit as a starting point (there is one for the upstream parent to
> the squash commit, stx-r1-upstream) if that would be helpful.
>
> dt
>




More information about the Starlingx-discuss mailing list