[Starlingx-discuss] stx-tools in manifest
Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default? I did not request that branch via -b. Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott
I agree, this needs to be pointing to master . Brent -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Friday, July 27, 2018 2:19 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx-tools in manifest Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default? I did not request that branch via -b. Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Abraham noted this earlier in his thread: " StarlingX Master Branch Successful Compilation". He mentions a workaround Al -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Friday, July 27, 2018 2:19 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx-tools in manifest Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default? I did not request that branch via -b. Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Fri, Jul 27, 2018 at 1:19 PM, Scott Little <scott.little@windriver.com> wrote:
Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default? I did not request that branch via -b. Shouldn't our default be the bleeding edge of master?
My error, https://review.openstack.org/584348 was committed against master not the m/2018.07 branch. I've cherry-picked that to the correct branch [0] and submitted a revert [1]. dt [0] https://review.openstack.org/586637 [1] https://review.openstack.org/586638 -- Dean Troyer dtroyer@gmail.com
participants (4)
-
Bailey, Henry Albert (Al)
-
Dean Troyer
-
Rowsell, Brent
-
Scott Little