/home/.config/htop/

	Commit message (Expand)	Author
2015-08-13	redirect: cleanliness	Jason A. Donenfeld
2015-08-13	redirect: be more careful for different cgi setups	Jason A. Donenfeld
2015-08-12	ui-log: fix double counting	John Keeping
2015-08-12	log: allow users to follow a file	John Keeping
2015-08-12	shared: make cgit_diff_tree_cb public	John Keeping
2015-08-12	t0110: Chain together using &&	Jason A. Donenfeld
2015-08-12	about: always ensure page has a trailing slash	Jason A. Donenfeld
2015-08-12	filters: apply HTML escaping	Lazaros Koromilas
2015-08-12	git: update to v2.5.0	Christian Hesse
2015-08-12	Fix processing of repo.hide and repo.ignore	Daniel Reichelt'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-28	ui-log: ignore unhandled arguments	John 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-28	git: update for git 2.0	Christian 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-17	remove trailing whitespaces from source files	Christian Hesse

2014-04-12	git: update to 1.9.2	Christian Hesse
	Everything works just bumping the version in Makefile and commit hash in submodule. No code changes required.
2014-04-05	Fix cgit_parse_url when a repo url is contained in another repo url	Julian 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-20	Makefile: use more reliable git tarball mirror	Jason A. Donenfeld

2014-03-20	git: update to 1.9.1	Christian Hesse