On Thu, Mar 29, 2018 at 5:21 AM, James E. Blair wrote:
> Hi,
>
> I've proposed a change to devstack which slightly alters the
> LIBS_FROM_GIT behavior. This shouldn't be a significant change for
> those using legacy devstack jobs (but you may want to be aware of it).
> It is
>
> Neither local nor third-party CI use should be affected. There's no
> change in behavior based on current usage patterns. Only the caveat
> that if you introduce an error into LIBS_FROM_GIT (e.g., a misspelled or
> non-existent package name), it will not automatically be caught.
>
> -Jim
Sean McGinnis writes:
> On Wed, Mar 28, 2018 at 07:37:19PM -0400, Doug Hellmann wrote:
>> Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
>> > Hi,
>> >
>> > I've proposed a change to devstack which slightly alters the
>> > LIBS_FROM_GIT behavior. This
On Wed, Mar 28, 2018 at 07:37:19PM -0400, Doug Hellmann wrote:
> Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
> > Hi,
> >
> > I've proposed a change to devstack which slightly alters the
> > LIBS_FROM_GIT behavior. This shouldn't be a significant change for
> > those using legacy
Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
> Hi,
>
> I've proposed a change to devstack which slightly alters the
> LIBS_FROM_GIT behavior. This shouldn't be a significant change for
> those using legacy devstack jobs (but you may want to be aware of it).
> It is more
Hi,
I've proposed a change to devstack which slightly alters the
LIBS_FROM_GIT behavior. This shouldn't be a significant change for
those using legacy devstack jobs (but you may want to be aware of it).
It is more significant for new-style devstack jobs.
The change is at