From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 2/2] gitweb: Add an option to show size of blobs in the tree view
Date: Thu, 2 Aug 2007 01:58:50 +0200 [thread overview]
Message-ID: <200708020158.50343.jnareb@gmail.com> (raw)
In-Reply-To: <7v3az24zo6.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> But I agree that this should be protected by the %feature mechanism.
>> Two questions:
>>
>> 1. Should we make '-l' default when turned on? Or make 'showsizes'
>> %feature tristate: off, on, by default on?
>>
>> 2. If it is turned off, should we silently (or not so silently)
>> ignore this option, or return "Permission denied" or perhaps
>> "Invalid extra options parameter"?
>>
>> And how we should name this feature (key in %feature hash)?
>
> I would say we would not do this by default, only with an
> explicit override with gitweb-config.perl. I am not sure what
> the good name would be. "expensive-ls-tree" perhaps?
So you think that ";opt=-l" would be required to have 'tree' view with
blob (file) sizes, and it would be allowed only if
gitweb_check_feature('ls-tree-size') is true (or something like that).
Should we return "Permission denied" or simply ignore "-l" extra option
if it is prohivited by the config?
As to good name: 'showsize'? 'ls-tree-size'? 'ls-tree--long'?
>> P.S. I have received no comments on
>> [RFC/PATCH] gitweb: Enable transparent compression for HTTP output
>> (trade CPU load for lower bandwidth usage).
>
> That's probably nobody was interested in it.
Well, it was also posted in the middle of old thread...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-08-01 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 11:19 [PATCH 1/2] gitweb: Allow for multivalued parameters passed to href subroutine Jakub Narebski
2007-07-31 11:19 ` [RFC/PATCH 2/2] gitweb: Add an option to show size of blobs in the tree view Jakub Narebski
2007-07-31 22:12 ` Junio C Hamano
2007-08-01 13:05 ` Jakub Narebski
2007-08-01 23:12 ` Junio C Hamano
2007-08-01 23:58 ` Jakub Narebski [this message]
2007-08-02 0:47 ` Junio C Hamano
2007-08-02 5:22 ` Junio C Hamano
2007-08-02 10:47 ` Jakub Narebski
2007-08-02 20:47 ` Junio C Hamano
2007-07-31 23:07 ` 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=200708020158.50343.jnareb@gmail.com \
--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 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 NNTP newsgroup(s).