| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
features from the settings menu and get rid of skill levels
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
is a tradeoff. It would be better to have one setting for both but if we want to preserve the *all settings* view, this would break its functionality
|
| |
|
|
|
|
| |
module settings
|
| |
|
| |
|
|
|
|
| |
link to settings in the navbar if present for a module and some code optimisation
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
settings text.
|
|\
| |
| | |
Auto-save comment and post text
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
Not for 3.2 as it requires string changes from the prior checkin.
|
|
|
|
| |
auto-enabling at various feature levels. This involves string changes and should *not* go into 3.2RC.
|
|
|
|
| |
filtering takes place
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
work)
|
| |
|
| |
|
| |
|
| |
|
| |
|