summary refs log tree commit diff
path: root/bin (follow)
Commit message (Collapse)AuthorAge
...
* Clean up klonJune McEnroe2018-02-25
|
* Clean up xxJune McEnroe2018-02-23
| | | | There are probably like 12 commits with this title.
* Clean up wakeJune McEnroe2018-02-23
|
* Avoid unnecessary FDs in errorsJune McEnroe2018-02-23
|
* Clean up pbdJune McEnroe2018-02-23
| | | | Seems probably a good idea to CLOEXEC sockets.
* Clean up fbclockJune McEnroe2018-02-23
| | | | | | | You can't use the return value of gzerror to check if an error occurred or not. Its implementation actually checks if the internal error is NULL and returns the empty string if it is! This is stupid and unhelpful, so check gzeof first since its return value actually means something.
* Don't bother checking result of close(2) in dtchJune McEnroe2018-02-23
|
* Tweak fbatt exit codesJune McEnroe2018-02-23
|
* Clean up dtch (again, probably)June McEnroe2018-02-23
| | | | | Mostly changes to exit codes and renaming len to size. Also no more writeAll.
* Return NOINPUT on execvp failureJune McEnroe2018-02-23
|
* Return EX_OSFILE in briJune McEnroe2018-02-23
|
* Rewrite briJune McEnroe2018-02-22
|
* Exit cleanly from hnel on LinuxJune McEnroe2018-02-22
| | | | Okay the change that actually does that is checking revents == POLLIN.
* Abort on other values of enums in pngoJune McEnroe2018-02-22
|
* Fix zlib types on 32-bitJune McEnroe2018-02-22
|
* Add unistd.h include to pngo.cJune McEnroe2018-02-20
| | | | Where getopt properly lives.
* Take multiple inputs to pngoJune McEnroe2018-02-20
|
* Reduce bit depth in pngoJune McEnroe2018-02-20
|
* Always use None filter for indexed or bit depth < 8June McEnroe2018-02-20
|
* Add pngo command line optionsJune McEnroe2018-02-19
|
* Clean up pngo optimization functionsJune McEnroe2018-02-19
|
* Index color if possible in pngoJune McEnroe2018-02-19
|
* Read and write palette in pngoJune McEnroe2018-02-19
|
* Add pngo to READMEJune McEnroe2018-02-18
|
* Always dump truecolor PNG in gfxxJune McEnroe2018-02-18
| | | | pngo can handle reducing it to grayscale.
* Eliminate redundant color in pngoJune McEnroe2018-02-18
|
* Just globalize all the things in pngoJune McEnroe2018-02-18
|
* Tweak pngo codeJune McEnroe2018-02-17
|
* Eliminate redundant alpha in pngoJune McEnroe2018-02-17
|
* Support all bit depths in pngoJune McEnroe2018-02-17
|
* Implement filter heuristic from PNG specJune McEnroe2018-02-17
|
* Fix pngo glitchJune McEnroe2018-02-16
| | | | | Basically changing the filter type without actually recalculating the bytes results in some interesting stuff.
* Refactor scanlines and filter bytes, more glitchJune McEnroe2018-02-16
|
* Fix paethPredictor comparisonJune McEnroe2018-02-16
|
* Handle more color types, depths, IDATs in pngoJune McEnroe2018-02-16
| | | | | Also fixed reconData so that it can at least round-trip the glitches it creates.
* Add WIP pngo which produces glitch artJune McEnroe2018-02-15
|
* Encode grayscale PNGs in gfxxJune McEnroe2018-02-14
|
* Avoid accessing past last byte in gfxxJune McEnroe2018-02-14
|
* Print PNG path on gfxx dumpJune McEnroe2018-02-14
|
* Add gfxx 4444 presetJune McEnroe2018-02-14
|
* Fix gfxx row scrolling for BITS_TOTAL < 8June McEnroe2018-02-14
|
* Write at least 1 for each component of sBIT in gfxxJune McEnroe2018-02-14
| | | | PNG requires each to be 0 < x <= depth. ImageMagick actually checks.
* Write newlines between watch iterationsJune McEnroe2018-02-14
|
* Add gfxx DUMP_ALLJune McEnroe2018-02-14
|
* Replace pngChunk with glorious C metaprogrammingJune McEnroe2018-02-14
|
* Move PNG filename counter into gfxxJune McEnroe2018-02-14
| | | | pngs.c was a fun idea but a little convoluted.
* Remove typoJune McEnroe2018-02-14
| | | | | The bin, not a typographical error. I only made it because I was switching keyboard layouts but now I'm back on QWERTY and can type fine.
* Unset dump in gfxx drawJune McEnroe2018-02-13
| | | | Otherwise hitting 'x' then resizing would cause dumps.
* Add PNG stream splitterJune McEnroe2018-02-13
| | | | | I don't know, somehow this is easier than having gfxx care about where it's writing to.
* Dump gfxx screen to PNG on stdout with xJune McEnroe2018-02-12
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-10-30 06:03:58 +0000
?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