--- Junio C Hamano <junkio@xxxxxxx> wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: > > > ... That means that we cannot distinguish really well (at > > least color) between tree and blob entries. > > Do we even say links are blue and underlined by forcing that in > our css? > > Doesn't leading drwxr-xr-x mean anything? > > Why is making the distinction important in the first place? > > > In the case of shortlog/log/history/heads/tags view, to clearly mark > > subject/title of a commit or tag as link, we would have to use default > > link decoration.... > > But underlined text is harder to read, and blue underlined text even > > more so... > > This is something in which I can see some more sense than tree > vs blob issue, but only as a principle issue. In practice, the > list of commit subjects is the first thing users encounter, and > as long as there is some visual indication (e.g. mousing over it > makes it obvious it is something that is clickable), I think > users will quickly pick up that it will lead to the commit's > detail. Very well put. Luben - 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