From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Two gitweb feature requests
Date: Sat, 29 Apr 2006 13:16:26 +0200 [thread overview]
Message-ID: <e2v46t$gu9$1@sea.gmane.org> (raw)
In-Reply-To: 1146144425.11909.450.camel@pmac.infradead.org
It would be nice if gitweb provided for the GIT repository description which
doesn't fit the "Description" column and is shortened, and any other text
which doesn't fit it's own column, full text of said field as the "title"
attribute for the cell 'td' element, or encompasing 'span' element. It
would result in having full, not shortened text of said field (e.g.
repository description) in the pop-up on mouse hover over said field. To
simplify things it could be provided unconditionally, regardless whether
the field needs shortening or not.
By the way, would it be possible for the repository without provided
description to stand out more, perhaps by changing formatting of default
description:
"Unnamed repository; edit this file to name it for gitweb."
to use ALL CAPS for attention, like that:
"UNNAMED REPOSITORY; edit this file to name it for gitweb."
or perhaps if possible use HTML formatting [additionally] for that.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-04-29 11:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 13:27 Two gitweb feature requests David Woodhouse
2006-04-27 13:35 ` Matthias Lederhofer
2006-04-27 13:47 ` David Woodhouse
2006-04-27 22:54 ` Ben Clifford
2006-04-29 21:38 ` David Woodhouse
[not found] ` <20060428122630.234edde4.seanlkml@sympatico.ca>
2006-04-28 16:26 ` sean
2006-04-28 17:37 ` Jakub Narebski
2006-04-28 18:23 ` Linus Torvalds
2006-04-28 19:11 ` Jakub Narebski
2006-04-29 5:02 ` Jeff King
2006-04-29 11:16 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-29 7:27 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='e2v46t$gu9$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).