summary refs log tree commit diff
Commit message (Expand)AuthorAge
...
* Fix gfxx draw stop conditionJune McEnroe2018-02-04
* Reuse CGColorSpace and CGDataProvider in gfcocoaJune McEnroe2018-02-04
* Mark mac target phonyJune McEnroe2018-02-04
* Set up Makefile for gfxx-cocoa or gfxx-fbJune McEnroe2018-02-04
* Avoid doing excessive work in gfxxJune McEnroe2018-02-04
* Handle window resizing in gfcocoaJune McEnroe2018-02-04
* Set cinoptionsJune McEnroe2018-02-04
* Tweak colorscheme moreJune McEnroe2018-02-04
* Color MatchParen DarkYellowJune McEnroe2018-02-04
* Add palette sampling to gfxxJune McEnroe2018-02-04
* Add 4-bit RGB to gfxxJune McEnroe2018-02-04
* Add Quit menu item to gfcocoaJune McEnroe2018-02-04
* Switch back to sane Objective-C styleJune McEnroe2018-02-04
* Quit gfcocoa when window closesJune McEnroe2018-02-04
* Apparently this is how people write Objective-CJune McEnroe2018-02-03
* Add dirty but working cocoa frontendJune McEnroe2018-02-03
* Separate gfxx and its framebuffer frontendJune McEnroe2018-02-03
* Add gfxx palette loadingJune McEnroe2018-02-02
* Fix color scaling in gfxxJune McEnroe2018-02-02
* Rework gfxx controlsJune McEnroe2018-02-02
* Add RGB and GRAY macros in gfxxJune McEnroe2018-02-02
* Add colorspaces and mirroring to gfxxJune McEnroe2018-02-02
* Set auto_pushdJune McEnroe2018-02-01
* Uncapitalize "framebuffer"June McEnroe2018-02-01
* Add fbattJune McEnroe2018-02-01
* Blank framebuffer with sampled background on exitJune McEnroe2018-02-01
* Add bin/READMEJune McEnroe2018-02-01
* Add license notice to gfxxJune McEnroe2018-02-01
* Build any target by defaultJune McEnroe2018-02-01
* Remove fb.c and color.cJune McEnroe2018-02-01
* Add gfxxJune McEnroe2018-02-01
* Map \h to sort includesJune McEnroe2018-01-31
* Only load 128 glyphs in fbclockJune McEnroe2018-01-31
* Style tweak fbclockJune McEnroe2018-01-30
* Remove Tarmak and Colemak keylayoutsJune McEnroe2018-01-30
* Generalize hnelJune McEnroe2018-01-29
* Remove Tarmak remappings from vimJune McEnroe2018-01-29
* Switch back to QWERTY on LinuxJune McEnroe2018-01-29
* Take fbclock font in env varJune McEnroe2018-01-29
* Support fbclock fonts wider than 8June McEnroe2018-01-29
* Take font path on fbclock argvJune McEnroe2018-01-29
* Add fbclockJune McEnroe2018-01-29
* Remove color from MakefileJune McEnroe2018-01-29
* Set t_Co = 8June McEnroe2018-01-29
* Add :Q command aliasJune McEnroe2018-01-29
* Add setuid target for briJune McEnroe2018-01-29
* Add init function to fb interfaceJune McEnroe2018-01-28
* Add color.cJune McEnroe2018-01-28
* Add fb.cJune McEnroe2018-01-28
* Add klon one line descriptionJune McEnroe2018-01-28
generated by cgit-pink 1.4.1 (git 2.36.1) at 2026-10-26 16:49:33 +0000
200'>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