summary refs log tree commit diff
Commit message (Expand)AuthorAge
* Track MODE in repliesJune McEnroe2020-03-23
* Fix non-multiline command newline handlingJune McEnroe2020-03-23
* Add M-Enter to insert a newlineJune McEnroe2020-03-23
* Handle bracketed paste, including newlinesJune McEnroe2020-03-23
* Allow commands to take multiline inputJune McEnroe2020-03-23
* Bump edit buffer cap to 1024June McEnroe2020-03-23
* Assume worst case for unknown user and host in splitMessageJune McEnroe2020-03-23
* Implement message splittingJune McEnroe2020-03-22
* Handle empty input directly in commandJune McEnroe2020-03-22
* Track own host, handle CHGHOSTJune McEnroe2020-03-22
* Add /sayJune McEnroe2020-03-22
* Handle RPL_CHANNELMODEISJune McEnroe2020-03-22
* Handle user mode changesJune McEnroe2020-03-22
* Rewrite handleModeJune McEnroe2020-03-22
* Handle RPL_UMODEISJune McEnroe2020-03-18
* Send blank line after 10 minutes idleJune McEnroe2020-03-17
* Ignore 422 ERR_NOMOTDJune McEnroe2020-03-09
* Set self.pos before handling the messageJune McEnroe2020-03-08
* Prevent entering commands in <debug> if restrictedJune McEnroe2020-03-02
* Implement the causal.agency/consumer capabilityJune McEnroe2020-02-29
* Add raw modes to mode messageJune McEnroe2020-02-25
* Handle changing setParamModes, paramModes and other channel modesJune McEnroe2020-02-25
* Fix handling EXCEPTS and INVEX without valuesJune McEnroe2020-02-25
* Add /mode, /except, /invex and handle lists repliesJune McEnroe2020-02-25
* Accumulate mode changes into a buffer for one messageJune McEnroe2020-02-23
* Handle ERR_CHANOPRIVSNEEDEDJune McEnroe2020-02-20
* Handle MODE changing channel list modesJune McEnroe2020-02-20
* Handle MODE setting channel prefix modesJune McEnroe2020-02-20
* Just use "b" to query ban listJune McEnroe2020-02-20
* Change ban list formattingJune McEnroe2020-02-20
* Rearrange some handlersJune McEnroe2020-02-20
* Handle RPL_INVITING when no invite-notifyJune McEnroe2020-02-20
* Handle ERR_BANLISTFULLJune McEnroe2020-02-20
* Add handlers for user-in-channel errorsJune McEnroe2020-02-20
* Add generic error reply handlerJune McEnroe2020-02-20
* Add /ban, /unban and handle ban list repliesJune McEnroe2020-02-19
* Format WHOIS signon date with %F %TJune McEnroe2020-02-19
* Apply word wrapping to tabs before setting alignJune McEnroe2020-02-19
* Remove bad continues in styleParse loopsJune McEnroe2020-02-19
* Various small cleanup in ui.cJune McEnroe2020-02-19
* Use the correct hostname in error messagemultiplexd2020-02-17
* Increase buffer size to 1024June McEnroe2020-02-17
* Accept Shift-M-0 through Shift-M-9 as wellJune McEnroe2020-02-17
* Only scroll after reflow if necessaryJune McEnroe2020-02-17
* Scroll the window only once during reflowJune McEnroe2020-02-17
* Various small cleanupsJune McEnroe2020-02-16
* Replace a lot of snprintf with a catf implementationJune McEnroe2020-02-16
* Add 379 to WHOIS responsesJune McEnroe2020-02-16
* Track EXCEPTS and INVEX modesJune McEnroe2020-02-16
* Add RFC 1459 and modern.ircdocs.horse referencesJune McEnroe2020-02-16
generated by cgit-pink 1.4.1 (git 2.36.1) at 2025-11-20 13:54:52 +0000
a href='/cgit-pink/commit/scan-tree.c?h=1.4.0&id=4b91269bdbc21a664cc56c26d6071c630560f2e0&follow=1'>remove debug fprinf() calls that sneaked in with commit 79c985Christian Hesse 2014-06-28git: update to 2.0.1Christian Hesse Everything works just bumping the version in Makefile and commit hash in submodule. No code changes required. 2014-06-28ui-patch: Flush stdout after outputting dataJohn Keeping It looks like cached patches are truncated to the nearest 1024-byte boundary in the patch body. E.g.: > mricon@nikko:[/tmp]$ wget -O no-cache > "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=6e1b4fdad5157bb9e88777d525704aba24389bee" ... > 2014-06-11 15:34:51 (80.4 MB/s) - ‘no-cache’ saved [4767] Patch is complete, without truncation. Next hit, with cache in place: > mricon@nikko:[/tmp]$ wget -O yes-cache > "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=6e1b4 > fdad5157bb9e88777d525704aba24389bee" ... > 2014-06-11 15:35:01 (17.0 MB/s) - ‘yes-cache’ saved [4096/4096] Length truncated to 4096. The cache on disk looks truncated as well, so the bug must me during the process of saving cache. The same is true for larger patches: > mricon@nikko:[/tmp]$ wget -O no-cache > "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=2840c566e95599cd60c7143762ca8b49d9395050" ... > 2014-06-11 15:41:33 (1.07 MB/s) - ‘no-cache’ saved [979644] 979644 bytes with a cache-miss > mricon@nikko:[/tmp]$ wget -O yes-cache > "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=2840c > 566e95599cd60c7143762ca8b49d9395050" ... > 2014-06-11 15:41:46 (1.05 MB/s) - ‘yes-cache’ saved [978944] 978944 (956KB exactly) with a cache-hit Since the "html" functions use raw write(2) to STDIO_FILENO, we don't notice problems with most pages, but raw patches write using printf(3). This is fine if we're outputting straight to stdout since the buffers are flushed on exit, but we close the cache output before this, so the cached output ends up being truncated. Make sure the buffers are flushed when we finish outputting a patch so that we avoid this. No other UIs use printf(3) so we do not need to worry about them. Actually, it's slightly more interesting than this... since we don't set GIT_FLUSH, Git decides whether or not it will flush stdout after writing each commit based on whether or not stdout points to a regular file (in maybe_flush_or_die()). Which means that when writing directly to the webserver, Git flushes stdout for us, but when we redirect stdout to the cache it points to a regular file so Git no longer flushes the output for us. The patch is still correct, but perhaps the full explanation is interesting! Reported-by: Konstantin Ryabitsev <mricon@kernel.org> 2014-06-28ui-log: ignore unhandled argumentsJohn Keeping If you search for a bogus range string here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/ Using something like "range" and "qwerty123456", it returns an "Internal Server Error" and the following in the logs: > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] fatal: > ambiguous argument 'qwerty123456': unknown revision or path not in the > working tree., referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Use '--' to > separate paths from revisions, like this:, referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] 'git <command> > [<revision>...] -- [<file>...]', referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > [Tue Jun 10 17:45:32 2014] [error] [client 172.21.1.6] Premature end > of script headers: cgit, referer: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ The cache will kick in, so if you search for the same string again, it'll show an empty range, so you have to change the bogus strings each time. This is because we just pass the arguments straight to Git's revision parsing machinery which die()s if it cannot parse an argument, printing the above to stderr and exiting. The patch below makes it a bit friendlier by just ignoring unhandled arguments, but I can't see an easy way to report errors when we can't parse revision arguments without losing the flexibility of supporting all of the revision specifiers supported by Git. Reported-by: Konstantin Ryabitsev <mricon@kernel.org> 2014-06-28git: update for git 2.0Christian Hesse prefixcmp() and suffixcmp() have been remove, functionality is now provided by starts_with() and ends_with(). Retrurn values have been changed, so instead of just renaming we have to fix logic. Everything else looks just fine. 2014-04-17remove trailing whitespaces from source filesChristian Hesse 2014-04-12git: update to 1.9.2Christian Hesse Everything works just bumping the version in Makefile and commit hash in submodule. No code changes required. 2014-04-05Fix cgit_parse_url when a repo url is contained in another repo urlJulian Maurice For example, if I have two repos (remove-suffix is enabled): /foo /foo/bar http://cgit/foo/bar/ is interpreted as "repository 'foo', command 'bar'" instead of "repository 'foo/bar'" 2014-03-20Makefile: use more reliable git tarball mirrorJason A. Donenfeld 2014-03-20git: update to 1.9.1Christian Hesse