viper-admin

> **@fabiopakk** on 2019-10-29 15:39: > * changed `state` from `new` to `resolved`

> **@alexanderjsummers** commented on 2019-10-29 15:42 Just a note: I don’t quite see how this issue relates to the fresh/constraining language features.

> **@fabiopakk** commented on 2019-10-30 10:31 Apparently Bitbucket used the commit messages to infer that an issue should be closed, unfortunately by mistake. My commits refer to issue 87 in...

> **@fabiopakk** commented on 2019-10-30 10:33 This issue was mistakenly closed by Bitbucket. That commit that caused such issue refers to an issue with the same number (87) but on...

> **@fabiopakk** on 2019-10-30 10:33: > * edited the description > * changed `state` from `resolved` to `open`

> **@Felalolf** on 2019-07-23 16:06: > * changed `priority` from `major` to `minor` > * edited the description

> **@MartinClochard** commented on 2019-07-23 18:50 Inaccurate.

> **@mschwerhoff** commented on 2014-01-26 14:05 was marked as a duplicate of this issue.

> **@mschwerhoff** on 2014-02-13 07:29: > * changed `component` from `(none)` to `Permissions`

> **@mschwerhoff** commented on 2014-03-18 08:57 A partial solution has been implemented with . The question about a generalised lookup strategy is still open, however, and of greater interest after...