~steering/inspircd++.git/make/template/config.h, branch v3.9.0 Unnamed repository; edit this file 'description' to name the repository. https://cgit.space/~steering/inspircd++.git/atom/make/template/config.h?h=v3.9.0 2021-02-26T06:58:13Z Update copyright headers. 2021-02-26T06:58:13Z InspIRCd Robot 2021-02-26T06:58:13Z urn:sha1:1bf7ca389426e196697eba9a8b60277db03fbedb Fix bitshift in INSPIRCD_VERSION_SINCE. 2021-01-30T17:31:40Z Sadie Powell 2021-01-30T17:31:40Z urn:sha1:10714b0ded0ff1304034bb3c2eab9ef5fb163616 Add a new runtime directory and move the pid file to it. 2021-01-18T07:05:27Z Sadie Powell 2021-01-18T06:56:18Z urn:sha1:a59ed4b39443eb788c15c65501898ca374387e2e The data directory is intended for persistent files whereas the pid file is ephemeral. This distinction doesn't matter by default but on system-wide installs ephemeral runtime files go in /var/run or /run instead. Replace the SERVER stub command with something actually useful. 2020-12-20T04:04:36Z Sadie Powell 2020-12-20T04:04:19Z urn:sha1:aa0221d87ca355d5021f81f8f65cf6a47bc93c38 This will typically never be reached because the remote will wait until it receives a CAPAB response before sending SERVER. Instead replace it with a CAPAB stub command that quits servers with a helpful message. Update copyright headers. 2020-07-30T13:31:12Z InspIRCd Robot 2020-07-30T13:31:12Z urn:sha1:2f12f76ec9561a6c1d522e3e6d81723ed9a07356 Fix the documentation comments in config.h. 2020-05-19T02:14:29Z Sadie Powell 2020-05-16T16:34:34Z urn:sha1:d2236175a369fd4d8f509c04beac80e31987a09f Update copyright headers. 2020-01-11T22:14:43Z InspIRCd Robot 2020-01-11T22:02:47Z urn:sha1:aa692dc1039b63deef7886e914ec499abe7facaf Update my name and email address. 2019-12-31T19:55:17Z Sadie Powell 2020-01-01T00:00:00Z urn:sha1:56375392ba94f2552bbeeeab4fd39e1e50295525 Clean up and document the config header file. 2019-05-13T14:22:14Z Peter Powell 2019-05-13T14:22:14Z urn:sha1:510f747854b17f64c2f597a4bd5743763fb518f4 Change the branch version from InspIRCd-3.0 to InspIRCd-3. 2018-10-25T22:29:55Z Peter Powell 2018-10-25T22:29:55Z urn:sha1:2b4682c2d1458377faa97ded0345d740ece31c66 Under the new versioning scheme when a new branch is forked the major version number will be reset. The minor version number will now be used to mark a release as containing backwards compatible additions and the patch version number will be used to mark a release as containing just bug fixes.