~steering/inspircd++.git/src/modules/m_topiclock.cpp, branch v3.0.0a6 Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/src/modules/m_topiclock.cpp?h=v3.0.0a6 2017-11-21T15:51:45Z Add the override keyword in places that it is missing. 2017-11-21T15:51:45Z Peter Powell 2017-11-21T13:05:17Z urn:sha1:91e0af0fc4889f20d2f63426f8fe379674fc0393 GCCs warnings for this are much better than Clangs. Convert uncontroversial anonymous numerics to use constants. 2017-09-06T09:44:41Z Peter Powell 2017-09-05T16:54:40Z urn:sha1:b13b1b8a0613e48013ca9f6a5279559d0aee0f73 Refactor topic setting logic to go through Channel::SetTopic() in all cases 2016-04-11T13:53:01Z Attila Molnar 2016-04-11T13:53:01Z urn:sha1:2706a993b3f8ee52e2728047fad6a56f7e3cf405 - Pass topic set time and optionally the setter to SetTopic() - Don't do anything if the topic is changed by a local user to what it is currently Convert WriteNumeric() calls to pass the parameters of the numeric as method parameters 2016-02-25T15:12:09Z Attila Molnar 2016-02-25T15:12:09Z urn:sha1:da29af8cba49d51e53d6e68237ccbf6370b6dd1f Specify which Extensible subclass an ExtensionItem is valid for 2015-01-18T09:40:33Z Attila Molnar 2015-01-18T09:40:33Z urn:sha1:4fc2f7199e964ba5112ecdb2613c6fd5c2eee638 Remove some dead code 2014-01-31T13:27:32Z Attila Molnar 2014-01-31T13:27:32Z urn:sha1:98ef89c392a63bb7a78df5e8d8283c848f9dd2af Introduce Server class 2014-01-05T14:04:01Z Attila Molnar 2014-01-05T14:04:01Z urn:sha1:11916574f67962dce1d7a2fdf7ef6a3d2d1fa49f - Replaces std::string server in User - Replaces InspIRCd::ULine() and SilentULine() Automatically register ServiceProviders created by modules 2013-09-08T15:11:08Z attilamolnar 2013-05-26T17:44:13Z urn:sha1:992674362c5f64bdb8e1942eeaa7612524529cd6 Automatically attach modules to events 2013-08-04T14:08:57Z attilamolnar 2013-08-04T12:36:14Z urn:sha1:d24619c012b34d5a3d4cfb93e7bea3ff3d5721e7 Change modules to use the MODNAME constant when logging. 2013-08-04T12:32:51Z Peter Powell 2013-07-07T19:01:44Z urn:sha1:abc57eddfb56462ac3e433601d010abf1942e611 The majority of modules were logging with their module name as the log type. There was a few places which were logging to a non-name type but, with the exception of CONFIG, those messages are so uncommon that it doesn't make sense to use a seperate type for them.