summary refs log tree commit diff
Commit message (Collapse)AuthorAge
...
* Add catgirl shottyJune McEnroe2019-07-16
|
* Fix SGRs 90 and 100June McEnroe2019-07-16
|
* Add up -tJune McEnroe2019-07-15
|
* Implement scrolling regionJune McEnroe2019-07-15
|
* Add CSI names to shotty -dJune McEnroe2019-07-14
|
* Ignore CSI tJune McEnroe2019-07-14
|
* Add more info to shotty man pageJune McEnroe2019-07-14
|
* Fix OSC PT handlingJune McEnroe2019-07-14
| | | | Undo gone wrong!
* Handle OSC in shottyJune McEnroe2019-07-14
|
* Add shotty -dJune McEnroe2019-07-14
|
* Add shotty -cJune McEnroe2019-07-13
|
* Add DL to shottyJune McEnroe2019-07-13
|
* Color html rather than bodyJune McEnroe2019-07-12
| | | | | If background-color is only set on body then overscroll in Safari reveals white.
* Make author consistent and update URLsJune McEnroe2019-07-12
|
* Merge repository text.causal.agencyJune McEnroe2019-07-12
|\
| * Move to www/text.causal.agencyJune McEnroe2019-07-12
| |
| * Add "Testing C"June McEnroe2018-12-21
| |
| * Add ULOCJune McEnroe2018-12-14
| |
| * Use col -b to strip formattingJune McEnroe2018-10-08
| | | | | | | | As suggested in man(1).
| * Add CAVEATS to "Pleasant C"June McEnroe2018-10-01
| |
| * Add "Pleasant C"June McEnroe2018-09-30
| |
| * Add "Writing mdoc"June McEnroe2018-09-27
| |
| * Use here documents in feed.shJune McEnroe2018-09-20
| |
| * Correct typo in Using MakeJune McEnroe2018-09-18
| |
| * Add atom feed generatorJune McEnroe2018-09-18
| |
| * Use install(1) to installJune McEnroe2018-09-17
| |
| * Make install target depend on text filesJune McEnroe2018-09-17
| |
| * Add "Using Make"June McEnroe2018-09-17
|
* Add new causal.agency with shotty shotsJune McEnroe2019-07-12
|
* Use -s to infer terminal sizeJune McEnroe2019-07-12
|
* Add DCH to shottyJune McEnroe2019-07-12
| | | | This makes htop mostly work. Scrolling region still missing.
* Support insert mode in shottyJune McEnroe2019-07-12
| | | | | This is how curses puts characters into the bottom-right cell of the terminal.
* Don't do carriage return on line feedJune McEnroe2019-07-11
|
* Interpret 256color-style SGRsJune McEnroe2019-07-11
|
* Use inline style rather than <b>, <i>, <u>June McEnroe2019-07-11
|
* Factor out clearJune McEnroe2019-07-11
|
* Add bright option to shottyJune McEnroe2019-07-11
|
* Output <b>, <i>, <u> in shottyJune McEnroe2019-07-11
|
* Ignore SM and RMJune McEnroe2019-07-10
|
* Add shotty man page and build itJune McEnroe2019-07-09
|
* Add up -cJune McEnroe2019-07-09
|
* Add options for default colors to shottyJune McEnroe2019-07-09
|
* Use char literals consistentlyJune McEnroe2019-07-08
|
* Add initial version of shottyJune McEnroe2019-07-08
| | | | | It isn't particularly compatible with anything but implements enough that some stuff will mostly work.
* Add ^S toggle to pteeJune McEnroe2019-07-08
|
* Document lack of window size propagationJune McEnroe2019-07-08
|
* Add pteeJune McEnroe2019-07-08
|
* Add Wild SeedJune McEnroe2019-07-08
|
* Add common includes to AGPL templateJune McEnroe2019-07-06
|
* Remove redundant includeJune McEnroe2019-07-06
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-02-17 17:05:51 +0000
='3' class='logmsg'> 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