Makefile: do not touch the git objects with `make clean` - others/cgit

diff options

author	Lars Hjemli <hjemli@gmail.com>	2008-07-22 19:58:37 +0200
committer	Lars Hjemli <hjemli@gmail.com>	2008-07-22 19:58:37 +0200
commit	a75968df103a938656599e0d2d9fd1ab4de5ea8a (patch)
tree	878dfe5cc2a000c6f1dd6ae68f284d4b2559a2f4 /cache.c
parent	bb7485e8d7932ba04a94714bfe6a86a1e323435c (diff)
download	cgit-a75968df103a938656599e0d2d9fd1ab4de5ea8a.tar.gz cgit-a75968df103a938656599e0d2d9fd1ab4de5ea8a.tar.bz2 cgit-a75968df103a938656599e0d2d9fd1ab4de5ea8a.zip

Makefile: do not touch the git objects with `make clean`

I've been avoiding `make clean` for a long time due to its eagerness to kill all the git objectfiles. Signed-off-by: Lars Hjemli <hjemli@gmail.com>

Diffstat (limited to '')

0 files changed, 0 insertions, 0 deletions

ars Hjemli3-14/+31 Add a global variable, cgit_max_lock_attemps, to avoid the possibility of infinite loops when failing to acquire a lockfile. This could happen on broken setups or under crazy server load. Incidentally, this also fixes a lurking bug in cache_lock() where an uninitialized returnvalue was used. Signed-off-by: Lars Hjemli <hjemli@gmail.com> 2006-12-11Let 'make install' clear all cachefilesLars Hjemli1-0/+2 Signed-off-by: Lars Hjemli <hjemli@gmail.com> 2006-12-11Fix cache algorithm loopholeLars Hjemli3-11/+16 This closes the door for unneccessary calls to cgit_fill_cache(). Noticed by Linus. Signed-off-by: Lars Hjemli <hjemli@gmail.com> 2006-12-10Add version identifier in generated filesLars Hjemli2-9/+14 Signed-off-by: Lars Hjemli <hjemli@gmail.com> 2006-12-10Add license file and copyright noticesLars Hjemli5-0/+372 Signed-off-by: Lars Hjemli <hjemli@gmail.com> 2006-12-10Add caching infrastructureLars Hjemli9-28/+353 This enables internal caching of page output. Page requests are split into four groups: 1) repo listing (front page) 2) repo summary 3) repo pages w/symbolic references in query string 4) repo pages w/constant sha1's in query string Each group has a TTL specified in minutes. When a page is requested, a cached filename is stat(2)'ed and st_mtime is compared to time(2). If TTL has expired (or the file didn't exist), the cached file is regenerated. When generating a cached file, locking is used to avoid parallell processing of the request. If multiple processes tries to aquire the same lock, the ones who fail to get the lock serves the (expired) cached file. If the cached file don't exist, the process instead calls sched_yield(2) before restarting the request processing. Signed-off-by: Lars Hjemli <hjemli@gmail.com>


context:
space:
mode: