From: Jakub Narebski <jnareb@gmail.com>
To: Bernt Hansen <bernt@alumni.uwaterloo.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] gitweb: Style all tables using CSS
Date: Mon, 19 Nov 2007 16:08:45 +0100 [thread overview]
Message-ID: <200711191608.46955.jnareb@gmail.com> (raw)
In-Reply-To: <87d4u671kx.fsf@gollum.intra.norang.ca>
Bernt Hansen wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > - print "<table cellspacing=\"0\">\n" .
> > + print "<table class=\"projects_list\">\n" .
>
> Should this class be "project_list" instead? I don't see a definition
> of "projects_list" (plural) anywhere.
Now that you mentioned it, I have checked and... we have a bit of
inconsistency in gitweb here. There are $projects_list and
$projects_list_description_width variables (plural),
git_get_projects_list subroutine (also plural), but view is called
'project_list', it is generated by git_project_list subroutine using
git_get_project_list_from_file and git_project_lis_body subroutines.
I am not native English speaker: gitweb mean here "list of projects".
We should probably uniqueify number to either plural or singular, and
not mixed as it is now. But this is a bit of nitpicking/paintshed...
Changing action name from 'project_list' would be hard because of
backward compatibility... _if_ we officially used this action; it is
default action when no project is selected, and all links use this
form.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-11-19 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 13:16 [PATCH 0/2] gitweb: CSS cleanup, part 1 Jakub Narebski
2007-11-19 13:16 ` [PATCH 1/2] gitweb: Style all tables using CSS Jakub Narebski
2007-11-19 14:27 ` Bernt Hansen
2007-11-19 15:08 ` Jakub Narebski [this message]
2007-11-19 13:16 ` [PATCH 2/2] gitweb: Put project README in div.readme, fix its padding 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=200711191608.46955.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=bernt@alumni.uwaterloo.ca \
--cc=git@vger.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.
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).