From: "Jan Stępień" <jan@stepien.cc>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: The "Owner" column can be hidden
Date: Wed, 31 Mar 2010 15:16:48 +0200 [thread overview]
Message-ID: <20100331151648.dbd8bd45.jan@stepien.cc> (raw)
In-Reply-To: <m3eij0iy5m.fsf@localhost.localdomain>
On Wed, 31 Mar 2010 03:28:24 -0700 (PDT)
Jakub Narebski <jnareb@gmail.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.
> >
>
> This commit message is a bit lacking, in that it does not describe
> *why* one would want to hide "Owner" column in projects list page.
> It is not described either why "Owner" column is unique among all
> other columns, in that it is the only column that can be hidden.
>
> Besides for completeness you might want to hide "Owner" row in project
> summary page.
>
The reason why I think gitweb should allow hiding the "Owner" row are
situations when its used for displaying a single person's repositories.
In such situation repeating the owner's name in each row may be
unnecessary in one's point of view and an option for hiding the whole
column could be a solution.
> > Signed-off-by: Jan Stępień <jstepien@users.sourceforge.net>
> > ---
> > gitweb/gitweb.perl | 9 ++++++---
> > 1 files changed, 6 insertions(+), 3 deletions(-)
>
> While "Gitweb config file variables" section in gitweb/README does not
> need to include _all_ gitweb configuration variables, you should thing
> about it whether to include description of '$show_owner_column' (or
> just '$show_owner') in gitweb/README, and whether to include note
> about this variable in "Projects list file format" in this file.
>
I agree with you on adding it to the "Gitweb config file variables"
section. On the other hand, I think that mentioning it in "Projects
list file format" isn't necessary unless '$show_owner' would affect the
way the projects list file would be parsed.
> >
> > diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> > index a2d2283..95f7f06 100755
> > --- a/gitweb/gitweb.perl
> > +++ b/gitweb/gitweb.perl
> > @@ -160,6 +160,9 @@ our @diff_opts = ('-M'); # taken from git_commit
> > # the gitweb domain.
> > our $prevent_xss = 0;
> >
> > +# presense of the projects list "Owner" column
>
> I'd rather have here
>
> +# If false, hide "Owner" column on projects list page, and "Owner" row
> +# in the project summary page.
>
Yes, that sounds better.
> > +our $show_owner_column = 1;
>
> Perhaps it should be '$show_owner', or '$hide_owner'.
>
Agreed. Given that displaying owner information is the default behaviour
I guess that "$hide_owner" or "$omit_owner" will be a better name for
it.
> BTW. if it would hide owner everywhere, you might want to skip
> generating / reading projects owners.
>
Broadening the scope of this variable and hiding owner information also
on the project info page is more than I initially thought of, but it
seems like a good idea. In this case I'll add skipping owner generation
to the next version of the patch.
Thanks for comments!
Cheers,
--
Jan Stępień <jan@stepien.cc>
next prev parent reply other threads:[~2010-03-31 13:25 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ń
2010-03-31 10:28 ` Jakub Narebski
2010-03-31 13:16 ` Jan Stępień [this message]
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=20100331151648.dbd8bd45.jan@stepien.cc \
--to=jan@stepien.cc \
--cc=git@vger.kernel.org \
--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.