From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2010, #05; Sat, 16)
Date: Sun, 17 Jan 2010 19:02:41 -0800 (PST) [thread overview]
Message-ID: <m38wbwcdzv.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vljfxa1o6.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jh/gitweb-cached (2010-01-13) 9 commits
Those two I think are not close to be ready
> - gitweb: File based caching layer (from git.kernel.org)
Large code dump. I am working (slowly) on splitting it.
> - gitweb: Convert output to using indirect file handle
Does not need two file handles. Style should probably be "print $out <sth>"
Thos could probably be merged soon (after final round of corrections)
> - gitweb: cleanup error message produced by undefined $site_header
It's not only $site_header
> - gitweb: add a get function to compliment print_sort_th
> - gitweb: add a get function to compliment print_local_time
O.K.
> - gitweb: Makefile improvements
I think it is O.K.
> - gitweb: Add option to force version match
Allow for version mismatch in test, add test for version match
> - gitweb: change die_error to take "extra" argument for extended die information
Minor fixup (commit message, whitespace). Otherwise O.K.
> - gitweb: Load checking
O.K., but needs a fixup to 'blame_incremental' related code. Some
assumptions can hold no longer
>
> Replaced with a re-roll. Update to t9500 is probably needed.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-01-18 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 2:46 What's cooking in git.git (Jan 2010, #05; Sat, 16) Junio C Hamano
2010-01-17 19:40 ` Jeff King
2010-01-18 3:02 ` Jakub Narebski [this message]
2010-01-18 6:30 ` Junio C Hamano
2010-01-28 21:16 ` Avery Pennarun
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=m38wbwcdzv.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.