All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Stępień" <jan@stepien.cc>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: The "Owner" column can be hidden
Date: Wed, 31 Mar 2010 15:32:18 +0200	[thread overview]
Message-ID: <20100331153218.6b13853b.jan@stepien.cc> (raw)
In-Reply-To: <7vy6h8om7q.fsf@alter.siamese.dyndns.org>

On Wed, 31 Mar 2010 02:48:57 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> Jan Stępień  <jstepien@users.sourceforge.net> writes:
> 
> > This commit adds $show_owner_column configuration variable which allows
> > to hide the project list "Owner" column if desired.
> > 
> > @@ -4430,7 +4433,7 @@ sub git_project_list_body {
> >  		}
> >  		print_sort_th('project', $order, 'Project');
> >  		print_sort_th('descr', $order, 'Description');
> > -		print_sort_th('owner', $order, 'Owner');
> > +		print_sort_th('owner', $order, 'Owner') if $show_owner_column;
> >  		print_sort_th('age', $order, 'Last Change');
> 
> Ugly.  Think what you would do if somebody else asks you to allow him to
> omit 'Description', or perhaps 'Last Change'.
> 
> I would understand if the change was to introduce a configuration variable
> of the array type @project_column whose default value is qw(project descr
> owner age) that is used to control which columns are shown in what order.
> 
> If it is undesirable to allow reordering the columns, the configuration
> should at least be %omit_project_column used like this, no?
> 
> 	print_sort_th('project', $order, 'Project')
>         	unless $omit_project_column{'project'};
> 	print_sort_th('descr', $order, 'Description')
>         	unless $omit_project_column{'descr'};
> 	...
> 

As I wrote in my e-mail to Jakub Narebski, the reason for hiding only
the "Owner" column is a single-user situation. There's only one owner
and repeating his name in each column isn't necessary.

I agree that your solution is cleaner and allows further customization,
but it covers a slightly different issue comparing to the one I'm
addressing.

I like the idea suggested by Jakub to make this config variable cover
other pages. It could remove the owner information from both the
project list and project summaries.

Cheers,
-- 
Jan Stępień <jan@stepien.cc>

  reply	other threads:[~2010-03-31 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:06 [PATCH] gitweb: The "Owner" column can be hidden Jan Stępień
2010-03-31  9:48 ` Junio C Hamano
2010-03-31 13:32   ` Jan Stępień [this message]
2010-03-31 10:28 ` Jakub Narebski
2010-03-31 13:16   ` Jan Stępień
2010-03-31 17:43     ` 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=20100331153218.6b13853b.jan@stepien.cc \
    --to=jan@stepien.cc \
    --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.