From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
"John 'Warthog9' Hawley" <warthog9@kernel.org>,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: What's cooking in git.git (Nov 2010, #02; Wed, 17)
Date: Thu, 18 Nov 2010 06:00:23 -0800 (PST) [thread overview]
Message-ID: <m3mxp668cy.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v1v6je9g8.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> --------------------------------------------------
> [Graduated to "master"]
> * bg/maint-gitweb-test-lib (2010-10-20) 1 commit
> (merged to 'next' on 2010-11-05 at 0ead869)
> + t/gitweb-lib: Don't pass constant to decode_utf8
> * jn/gitweb-test (2010-09-26) 4 commits
> (merged to 'next' on 2010-11-05 at 90b3adf)
> + gitweb/Makefile: Include gitweb/config.mak
> + gitweb/Makefile: Add 'test' and 'test-installed' targets
> + t/gitweb-lib.sh: Add support for GITWEB_TEST_INSTALLED
> + gitweb: Move call to evaluate_git_version after evaluate_gitweb_config
> (this branch is used by jh/gitweb-caching.)
Thanks.
Sidenote: recently sent
gitweb: selectable configurations that change with each request
practically reverts
gitweb: Move call to evaluate_git_version after evaluate_gitweb_config
Just FYI.
> --------------------------------------------------
> [New Topics]
> * gb/gitweb-remote-heads (2010-11-11) 11 commits
> - git instaweb: enable remote_heads
> - gitweb: group remote heads by remote
> - gitweb: provide a routine to display (sub)sections
> - gitweb: refactor repository URL printing
> - gitweb: remotes view for a single remote
> - gitweb: allow action specialization in page header
> - gitweb: nagivation menu for tags, heads and remotes
> - gitweb: separate heads and remotes lists
> - gitweb: git_get_heads_list accepts an optional list of refs
> - gitweb: introduce remote_heads feature
> - gitweb: use fullname as hash_base in heads link
>
> Acked by Jakub. Will merge to next.
Thanks.
> * jn/gitweb-time-hires-comes-with-5.8 (2010-11-09) 1 commit
> - gitweb: Time::HiRes is in core for Perl 5.8
>
> Looked reasonable. Will merge to next.
Thanks. With or without improvement to commit message?
> --------------------------------------------------
> [Stalled]
> * jh/gitweb-caching (2010-11-01) 4 commits
> . gitweb: Minimal testing of gitweb caching
> . gitweb: File based caching layer (from git.kernel.org)
> . gitweb: add output buffering and associated functions
> . gitweb: Prepare for splitting gitweb
>
> Temporarily ejected while I shuffled jn/gitweb-testing; will queue the
> latest back in pu or perhaps in next.
The advantage of 'gitweb: File based caching layer (from git.kernel.org)'
is that it is tested in real-life on heavy load (assuming that
git.kernel.org uses the same version as is/would be in pu/next).
The disadvantage is that it is seriously messy code. Something that I
wanted to improve in my rewrite. This is only minimal fixup.
I am thinking about splitting main 'gitweb: File based caching layer
(from git.kernel.org)' patch in two, separating moving test for
$caching_enabled out of cache_fetch to separate commit (largest change
to original J.H. submission), but leaving hardening "do 'cache.pl';"
and replacing 0/1 valued $cache_enable with boolean valued
$caching_enabled.
Because currently new tests in t9501 and t9502 (examining status and
output of gitweb with caching enabled) do not pass, I am thinking
about adding new configuration know turning off "Generating..." page.
BTW. should I forge J.H. signoffs, and add mine?
> * tr/config-doc (2010-10-24) 2 commits
> . Documentation: complete config list from other manpages
> . Documentation: Move variables from config.txt to separate file
>
> This unfortunately heavily conflicts with patches in flight...
Would creating a script for generating contents of 'Documentation:
Move variables from config.txt to separate file', including it either
in commit message or in comments, help this issue?
There is also problem with 'Documentation: complete config list from
other manpages' in that it needs (at least in one version) for all
config sections to be marked as such (see discussion in thread).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-11-18 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 0:56 What's cooking in git.git (Nov 2010, #02; Wed, 17) Junio C Hamano
2010-11-18 14:00 ` Jakub Narebski [this message]
2010-11-18 17:54 ` Junio C Hamano
2010-11-18 21:33 ` J.H.
2010-11-20 0:42 ` Jakub Narebski
2010-11-24 1:45 ` J.H.
2010-11-24 17:13 ` Junio C Hamano
2010-11-24 21:30 ` Jakub Narebski
2010-11-24 21:26 ` Jakub Narebski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mxp668cy.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).