Re: [PATCH] gitweb: support the rel=vcs microformat
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Jan 10, 2009, 00:01 UTC
- Message-ID
- <m3k594111k.fsf@localhost.localdomain>
- In-Reply-To
- <20090107184113.GA31795@gnu.kitenet.net>
Joey Hess <joey@kitenet.net> writes:
> Giuseppe Bilotta wrote: > > Joey Hess <joey@kitenet.net> writes:
Show 13 quoted lines
> > > Thanks for the feedback. There are some changes happening to the > > > microformat that should make gitweb's job slightly easier, I'll respin > > > the patch soon. > > > > Let me know about this too, I very much like the idea of this microformat. > > FYI, I've updated the microformat's page with the changes. The > significant one for gitweb is that it can now be applied to <a> links. > So on the project page, the display of the git URL could be converted to > a link using the microformat, and there's no need to get the info > earlier to put it in the header. Unfortunatly, the same can't be done to > the project list page, unless it's changed to have "git" links as seen > on vger.kernel.org's gitweb.
I'm not sure if making repository URLs to be hyperlinks is a good idea. You cannot (should not) click on those in ordinary web browser; they are to be used by git (that is also additional reason why I am not so sure about 'git' link on projects_list page idea).
Besides LINK elements in page HEAD are meant mainly for machine; I think it might be more important to add them for machine there, even if they are as A elements (links) or just plain text URLs somewhere else. For example we have LINK elements with alternate versions, among others OPML for projectless pages, and RSS/Atom for project pages, aven though those links are also in page body.
So I'd rather have them LINKs...
-- Jakub Narebski Poland ShadeHawk on #git