Junio C Hamano wrote: > Jakub Narebski <jnareb@xxxxxxxxxxxxxxxxxxx> writes: (the above is result of paste in wrong place in git-send-email invocation) [...] >> The fix is to add "subject" class and use this class >> to replace pre-format_subject_html formatting of subject >> (comment) via using (or not) <b>...</b> element. This >> should go back to the pre-17d0744318... style. [...] > > I haven't seen an Ack from Luben for the proposed renaming of > the class, although I very much like naming things for what they > mean (i.e. "subject"), not what they do (i.e. "bold") myself. > > 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: <11562431392439-git-send-email-jnareb@xxxxxxxxxxxxxxxxxxx> 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). -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html