From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
"John 'Warthog9' Hawley" <warthog9@eaglescrag.net>,
"John 'Warthog9' Hawley" <warthog9@kernel.org>
Subject: Re: What's cooking in git.git (Jan 2010, #07; Fri, 22)
Date: Sat, 23 Jan 2010 03:18:17 -0800 (PST) [thread overview]
Message-ID: <m3my05ax5v.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vtyudfqju.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jh/gitweb-cached (2010-01-13) 9 commits
> - gitweb: File based caching layer (from git.kernel.org)
> - gitweb: Convert output to using indirect file handle
> - gitweb: cleanup error message produced by undefined $site_header
> - gitweb: add a get function to compliment print_sort_th
> - gitweb: add a get function to compliment print_local_time
> - gitweb: Makefile improvements
> - gitweb: Add option to force version match
> - gitweb: change die_error to take "extra" argument for extended die information
> - gitweb: Load checking
>
> Replaced with a re-roll. Update to t9500 is probably needed.
I have sent proof of concept replacements for the last two
patches... and those do include update to t9500 (although caching is
tested only rudimentally).
I don't know if J.H. is working on replacement patches; I am planning
on re-rolling cleaned up version of split file based caching layer on
top of his changes / his re-roll.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-01-23 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 3:28 What's cooking in git.git (Jan 2010, #07; Fri, 22) Junio C Hamano
2010-01-23 11:18 ` Jakub Narebski [this message]
2010-01-23 16:37 ` Jens Lehmann
2010-01-23 20:03 ` Junio C Hamano
2010-01-24 2:11 ` Junio C Hamano
2010-01-24 8:10 ` Junio C Hamano
2010-01-24 14:09 ` Jens Lehmann
2010-01-25 18:05 ` [RFC/H] "git diff --submodule" showing submodule work tree dirtiness Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3my05ax5v.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=warthog9@eaglescrag.net \
--cc=warthog9@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.