payload: {"push_id":3318606367,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"160c500a8c5384c3d00044c977c660997f2f00be","before":"86a1238c9fa45e929700d008c7a894a384426603","commits":[{"sha":"f8020ca4e024f584439eb88f67b27c7b9acc64e9","author":{"name":"multiplexd","email":"fa119f8dd2bd5910063d13016a3ad5909aebf2d8@in-addr.xyz"},"message":"Clean up the tokeniser to handle colons and numeric lines better.\n\nPreviously, before the tokeniser was run on each line, the TOK_TEXT\npointer was set to the char following the first colon found in the\nline starting at the argv[TOK_CMD]'th char. This breaks when\nprocessing MODE lines which use the extban syntax found in some IRC\nservers, as this would kill off the text including and following the\ncolon in the ban parameter. The beginning of the TOK_TEXT'th command\nargument is now handled by detecting a colon immediately following a\ndelimiter in the tokeniser itself to correctly handle this case.\n\nThe tokeniser's special casing for numeric lines (such as 005, 353,\netc) changes the delimiter character mid-tokenisation, which causes\nissues when parsing IPv6 addresses in hostmasks (cf. disabling\nhostname cloaking on networks where it's supported); further\ninvestigation reveals that various numeric lines are parsed\ninconsistently, so punt out of tokenisation on the first delimiter\n(i.e. space) after finding a TOK_CMD and a TOK_CHAN whenever a numeric\nline is found.\n\n(Speaking of the tokeniser, the fix to correctly detect numeric lines\nin a portable manner is now a year old. Happy birthday, commit\n257f6c7f34.)","distinct":true,"url":"https://api.github.com/repos/multiplexd/ii/commits/f8020ca4e024f584439eb88f67b27c7b9acc64e9"},{"sha":"c1486339b19c211db75c47cc9b41feca9d029d97","author":{"name":"multiplexd","email":"fa119f8dd2bd5910063d13016a3ad5909aebf2d8@in-addr.xyz"},"message":"Adapt the 353 message handler for the previous tokeniser changes.","distinct":true,"url":"https://api.github.com/repos/multiplexd/ii/commits/c1486339b19c211db75c47cc9b41feca9d029d97"},{"sha":"ae49d7fecb070e4c497e133ce69d50972e9559f4","author":{"name":"multiplexd","email":"fa119f8dd2bd5910063d13016a3ad5909aebf2d8@in-addr.xyz"},"message":"Fix NICK message parsing.\n\nInspircd is the only IRC server software I've come across which actually\nsends RFC-compliant NICK messages. *Every* *other* *server* adds a\nspurious colon -- while this does make the parsing machinery nicer\n(depending on how \"nice\" you think IRC is from a parsing standpoint),\nbut it means that on inspircd networks nick changes cannot be detected.\nThis is fixed by duplicating the NICK branch in the server message\nhandler to check the TOK_CHAN'th token as well as TOK_TEXT'th token.","distinct":true,"url":"https://api.github.com/repos/multiplexd/ii/commits/ae49d7fecb070e4c497e133ce69d50972e9559f4"},{"sha":"160c500a8c5384c3d00044c977c660997f2f00be","author":{"name":"multiplexd","email":"fa119f8dd2bd5910063d13016a3ad5909aebf2d8@in-addr.xyz"},"message":"Corner case for normalising channelmaster","distinct":true,"url":"https://api.github.com/repos/multiplexd/ii/commits/160c500a8c5384c3d00044c977c660997f2f00be"}]}
other: {"actor":{"display_login":"multiplexd"}}