summary refs log tree commit diff
path: root/etc (follow)
Commit message (Collapse)AuthorAge
...
* Tabify shell scriptsJune McEnroe2018-05-13
|
* Add demoman configJune McEnroe2018-04-22
| | | | Haven't tested it yet but should be good for hybrid knight.
* Add TF2 configsJune McEnroe2018-04-15
|
* Output Linux console escapes from schemeJune McEnroe2018-03-31
|
* Brighten color schemeJune McEnroe2018-03-31
|
* Set Dark terminal to schemeJune McEnroe2018-03-31
|
* Set Light terminal white to Gruvbox fg3June McEnroe2018-02-28
|
* Switch to and vendor Go Mono fontJune McEnroe2018-02-21
| | | | | | | Go Mono is almost identical to Luxi Mono (same designers) but MIT-licensed. From https://go.googlesource.com/image font/gofont/ttfs.
* Remove Tarmak and Colemak keylayoutsJune McEnroe2018-01-30
|
* Switch back to QWERTY on LinuxJune McEnroe2018-01-29
| | | | | I think the only thing I'll miss is N and E on home row (which was Tarmak 1, if I remember correctly).
* Fix CodeQWERTY layoutJune McEnroe2018-01-27
| | | | | | Based on the Canadian layout file from Ukelele with the same modifications I've been making to the Tarmak layouts so that control and command use the default layout.
* Add CodeQWERTY keylayoutJune McEnroe2018-01-27
| | | | | Yeah, I think it's time to switch back. My typing seems still worse than it started, and keeping weird layouts is inconvenient.
* Convert to CodeColemak keylayoutJune McEnroe2018-01-26
|
* Add Colemak keylayoutJune McEnroe2018-01-26
|
* Remove Code Tarmak 3June McEnroe2017-12-31
|
* Update Linux console map to Tarmak 4June McEnroe2017-09-27
|
* Add Code Tarmak 4 layoutJune McEnroe2017-09-27
| | | | So close now!
* Rename files directory etcJune McEnroe2017-09-15
|
* Remove unused configsJune McEnroe2013-10-14
|
* Update system configurationsJune McEnroe2013-04-24
|
* Add PulseAudio configurationJune McEnroe2012-12-19
|
* Remove rc.confJune McEnroe2012-12-19
|
* Add cpupower configurationJune McEnroe2012-10-06
|
* Add system-wide configuration filesJune McEnroe2012-10-06
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