It would be useful if we were able to allow a locked task to "freewheel" i.e. the locked task behaves as if it were unlocked, but any dependent tasks that aren't in that mode see the task as having the locked signature value. You could use this for example if you wanted to modify the kernel or glibc with "devtool modify" without having anything else rebuild in response to any of the changes.
(... without having to set a lock for all of those dependent tasks)
Richard to review but perhaps assign to another team member.
Build move to 5.0 -- ../Randy
Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue.
Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please.
This could be an option to bblock, Instead of "lock glibc", we'd want a "lock everything that depends on glibc" option.