Jakub Narebski wrote:
> Lea Wiemann wrote:
>> Gitweb's cache is actually never out-of-date
>
> Could you explain then how gitweb cache is invalidated?
Sure; from gitweb.perl:
# Transient cache entries (like get_sha1('HEAD')) are automatically
# invalidated when an mtime of either the repository's root directory
# or of the refs directory or any subdirectory changes. This
# mechanism *should* detect changes to the repository reliably if you
# only use git or rsync to write to it,
IOW, gitweb will do a small number of (inexpensive) stat calls on those
directories each time it's called, and use the most recent mtime as part
of the cache key for transient entries. Hence those transient entries
will automatically become invalid once the most recent mtime changes.
(If any of the relevant directories has been modified since the last
time gitweb checked, gitweb will re-scan the whole tree to check for new
directories, and record their mtimes as well. See get_last_modification
if you're interested in more gory details.)
The punchline is, the cache never returns outdated data.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
