summary refs log tree commit diff
path: root/bin/man1 (follow)
Commit message (Expand)AuthorAge
* Add bibsortJune McEnroe2020-12-15
* Add modem -r flag to set baud rateJune McEnroe2020-12-08
* Remove editJune McEnroe2020-10-29
* Open /dev/tty in nudgeJune McEnroe2020-09-04
* Add nudgeJune McEnroe2020-09-04
* Read from stdin in orderJune McEnroe2020-07-18
* Remove aesJune McEnroe2020-06-17
* Allow redirecting input in everJune McEnroe2020-06-01
* Add c scriptJune McEnroe2020-05-31
* Remove setoptJune McEnroe2020-03-03
* Revert "Add first working version of imbox"June McEnroe2019-12-21
* Add first working version of imboxJune McEnroe2019-12-21
* Add option to default to text in hiJune McEnroe2019-12-15
* Document diff input language in hiJune McEnroe2019-12-11
* Replace shotty with code from streamJune McEnroe2019-11-25
* Add title -v flagJune McEnroe2019-09-10
* Add -x flag to titleJune McEnroe2019-09-07
* Add titleJune McEnroe2019-09-05
* Add long-missing setopt to bin.7June McEnroe2019-08-29
* Add editJune McEnroe2019-08-29
* Rename wat to everJune McEnroe2019-08-28
* Remove brot and gfxxJune McEnroe2019-08-28
* Use rand(3) in beefJune McEnroe2019-08-28
* Remove wakeJune McEnroe2019-08-28
* Make dtch one command, add sinkingJune McEnroe2019-08-12
* Add whenJune McEnroe2019-07-24
* Handle media copy sequence in shottyJune McEnroe2019-07-20
* Handle shotty output options more centrallyJune McEnroe2019-07-20
* Add ^Q to ptee for MC sequenceJune McEnroe2019-07-17
* Add up -tJune McEnroe2019-07-15
* Add more info to shotty man pageJune McEnroe2019-07-14
* Add shotty -dJune McEnroe2019-07-14
* Add shotty -cJune McEnroe2019-07-13
* Use -s to infer terminal sizeJune McEnroe2019-07-12
* Add bright option to shottyJune McEnroe2019-07-11
* Add shotty man page and build itJune McEnroe2019-07-09
* Add up -cJune McEnroe2019-07-09
* Add ^S toggle to pteeJune McEnroe2019-07-08
* Document lack of window size propagationJune McEnroe2019-07-08
* Add pteeJune McEnroe2019-07-08
* Add CSS output to schemeJune McEnroe2019-07-06
* Add variables to bitJune McEnroe2019-06-07
* Simplify and build bitJune McEnroe2019-05-30
* Add xx -p optionJune McEnroe2019-05-29
* Add compound assignment operators to orderJune McEnroe2019-05-18
* Support simple assignment in orderJune McEnroe2019-05-15
* Implement sizeof in orderJune McEnroe2019-05-15
* Add orderJune McEnroe2019-05-15
* Move relay to binJune McEnroe2019-05-04
* Add setoptJune McEnroe2019-02-24
parsing.c: make commit buffer constJohn Keeping This will be required in order to incorporate the changes to commit buffer handling in Git 2.0.2. Signed-off-by: John Keeping <john@keeping.me.uk> 2014-06-30Bump version.Jason A. Donenfeld 2014-06-29remove 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