Re: fixing ci failure of 'pu' with the es/bugreport topic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes:

> Hm, ok. I'll send a reroll squashing this in verbatim tomorrow unless
> I hear otherwise from Dscho? Looks like it's indeed the first one
> (dd763e).
> I'm curious to know how I can check this build method for myself for next time.
>
> (If I misunderstood and I should send a reroll ASAP, please let me
> know; otherwise I already switched off for the evening.)

Nah, I do not think it is all that urgent.  I'd rather wait until we
hear positive "yup, that's the right way to do it" (or "no, you'd do
it this way instead" guidance) to waste an extra round.

Having said that, the topic won't touch 'next' with a known CI
glitch whose fix ought to be straight-forward especially with
help/nod from experts, and as far as I recall, there wasn't any
other outstanding issues for this round, even though we may already
have plans for possible follow-up enhancements, so let's not keep it
hanging unnecessarily longer.  Perhaps we'd all be happy if we can
resolve it before the end of this week or early next week?

Thanks.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux