Matěj Suchánek 3f34308f96 Tag actions which hit the condition limit ... When an action reaches the limit, the remaining filters are not executed. But there is no way find out which one it was. Bug: T71492 Change-Id: I28fac76d4e9ca341bed25cd35e1249b19586b773		2018-02-15 10:06:08 +01:00
..
api	Select only needed columns in queries	2018-02-10 20:35:05 +00:00
pagers	Move classes to own files	2017-12-23 13:43:37 +00:00
parser	Up at-ease calls in extensions	2018-02-12 10:31:55 +00:00
special	Select only needed columns in queries	2018-02-10 20:35:05 +00:00
Views	Select only needed columns in queries	2018-02-10 20:35:05 +00:00
AbuseFilter.class.php	Tag actions which hit the condition limit	2018-02-15 10:06:08 +01:00
AbuseFilter.hooks.php	Tag actions which hit the condition limit	2018-02-15 10:06:08 +01:00
AbuseFilterChangesList.php	Move classes to own files	2017-12-23 13:43:37 +00:00
AbuseFilterModifyLogFormatter.php	Actually mark abusefilter creations as such in the AbuseFilter log	2018-01-12 17:03:13 +00:00
AbuseFilterPreAuthenticationProvider.php
AbuseFilterVariableHolder.php	Improve some parameter docs	2017-10-07 00:54:58 +02:00
AbuseLogHitFormatter.php	Cleanup, added spaces	2017-10-19 09:40:22 +02:00
AFComputedVariable.php	Improve some parameter docs	2017-10-07 00:54:58 +02:00
TableDiffFormatterFullContext.php	Move classes to own files	2017-12-23 13:43:37 +00:00