about summary refs log tree commit diff
path: root/filters (follow)
Commit message (Expand)AuthorAge
* remove trailing whitespaces from source filesChristian Hesse2014-04-17
* filter: add libravatar email-filter lua scriptChristian Hesse2014-03-13
* simple-authentication: styleJason A. Donenfeld2014-01-23
* auth: document tweakables in lua scriptJason A. Donenfeld2014-01-17
* auth: have cgit calculate login addressJason A. Donenfeld2014-01-16
* auth: lua string comparisons are time invariantJason A. Donenfeld2014-01-16
* authentication: use hidden form instead of refererJason A. Donenfeld2014-01-16
* auth: add basic authentication filter frameworkJason A. Donenfeld2014-01-16
* email-gravatar: fix html syntax issuesChristian Hesse2014-01-15
* email-gravatar: do not scale icons upJason A. Donenfeld2014-01-14
* filter: allow returning exit code from filterJason A. Donenfeld2014-01-14
* email-gravatar: fix html syntax issuesChristian Hesse2014-01-14
* email-gravatar.py: fix UTF-8Christian Hesse2014-01-14
* email-gravatar.lua: fix for lua 5.2Christian Hesse2014-01-14
* filter: add page source to email filterJason A. Donenfeld2014-01-14
* filter: add gravatar scriptsJason A. Donenfeld2014-01-14
* filters: Improved syntax-highlighting.pyStefan Tatschner2014-01-13
* Fix UTF-8 with syntax-highlighting.pyPřemysl Janouch2014-01-08
* Fix about-formatting.shPřemysl Janouch2014-01-08
* filters: highlight.sh: add css comments for highlight 2.6 and 3.8Ferry Huberts2014-01-08
* filters: toggle perl utf8 situationJason A. Donenfeld2013-05-28
* filters: import more modern scriptsJason A. Donenfeld2013-05-27
* syntax-highlighting.sh: Fix command injection.Jason A. Donenfeld2012-10-27
* syntax-highlight: when the file has no extension, assume textFerry Huberts2012-10-09
* Revert "filters/syntax-highlighting.sh: work around highlight --force bug"Ferry Huberts2012-10-09
* Merge branch 'stable'Lars Hjemli2012-03-18
|\
| * filters/syntax-highlighting.sh: work around highlight --force bugFerry Huberts2012-03-18
| * filters/highlight.sh: manually support highlight version 2 and 3Ferry Huberts2012-03-18
* | commit-links.sh: improve regular expressionsFerry Huberts2011-07-19
* | filters: document environment variables in filter scriptsFerry Huberts2011-03-26
|/
* commit-links.sh: Seperate the expressions for filtering commit messages.Jeff Smith2010-07-22
* syntax highlighting for all formats supported by "highlight"Georg Lukas2009-11-19
* Add some example filter scriptsLars Hjemli2009-08-09
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-03 02:32:07 +0000
gt; 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