Re: [PATCH] gitweb: bugfix: a.list formatting regression

Jakub Narebski [off-list ref] writes:

Junio C Hamano wrote:

quoted

It might be worthwhile to do a full sweep of the pages we
generate and identify what classes we would want.  I have a
feeling that we overuse a.list for example -- they are all in
some form of list alright but they might benefit from a bit
finer logical separatoin.  One list is enumaration of refs and
another is a chronological sequence of commits.

Then people who would want to tweak the presentation would have
an easier time changing only gitweb.css.

Next patch in this series of patches 
   [PATCH] gitweb: Replace some presentational HTML by CSS
   Message-Id: [ref]
adds "name" subclass (a.list.name) for ref names. (I think
subclasses/multiple classes is the way to do it, as all a.list
elements have something in common: use next class to divide).

I agree about the implementation aspect, such as using
"list.name" as class names; I was suggesting to start from
design.