From: "J.H." <warthog9@kernel.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #02; Wed, 17)
Date: Thu, 18 Nov 2010 13:33:49 -0800 [thread overview]
Message-ID: <4CE59BBD.9060105@kernel.org> (raw)
In-Reply-To: <7v1v6icyb0.fsf@alter.siamese.dyndns.org>
>> 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?
>
> Just ping him beforehand ;-)
I hadn't done a signoff as Jakub asked me to investigate some breakage
in the testing infrastructure he had put together. Sadly I haven't been
able to duplicate it, and I haven't been able to catch him online to try
and figure out what the problem was exactly.
That said there's already a way to disable the Generating... page so I'm
not sure why an extra, and different, mechanism to disable it is needed...
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2010-11-18 21:33 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
2010-11-18 17:54 ` Junio C Hamano
2010-11-18 21:33 ` J.H. [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE59BBD.9060105@kernel.org \
--to=warthog9@kernel.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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.