I'm not sure either. I was hoping to freeze release_30 so we can merge and
be done with it. However the need to do a forthnightly update where we fix
loading of 17, 18 map formats means that it won't really be frozen. I guess
let's put it in, at the risk of starting a slippery slope that we just
never get rid of release_30...
On Sun, Mar 26, 2017 at 2:05 PM Stephen Lyons <email address hidden>
wrote:
I have a PR to push out against the release_30 branch that does this but
am not yet sure whether that is the place to request a pull against...
I'm not sure either. I was hoping to freeze release_30 so we can merge and
be done with it. However the need to do a forthnightly update where we fix
loading of 17, 18 map formats means that it won't really be frozen. I guess
let's put it in, at the risk of starting a slippery slope that we just
never get rid of release_30...
On Sun, Mar 26, 2017 at 2:05 PM Stephen Lyons <email address hidden>
wrote:
I have a PR to push out against the release_30 branch that does this but
am not yet sure whether that is the place to request a pull against...
-- /bugs.launchpad .net/bugs/ 1675988
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
3.0 regression: search field no longer stays visible
To manage notifications about this bug go to: /bugs.launchpad .net/mudlet/ +bug/1675988/ +subscriptions
https:/