Giuseppe Bilotta <giuseppe.bilotta@xxxxxxxxx> writes: > On Wednesday 07 January 2009 05:25, Joey Hess wrote: > > > The rel=vcs microformat allows a web page to indicate the locations of > > repositories related to it in a machine-parseable manner. > > (See http://kitenet.net/~joey/rfc/rel-vcs/) > > Interesting idea, I like it. However, I see a problem in the proposed > implementation versus the spec. According to the spec: > > """ > The "title" is optional, but recommended if there are multiple, different > repositories linked to on one page. It is a human-readable description of the > repository. > [...] > If there are multiple repositories listed, without titles, tools > should assume they are different repositories. > """ Good catch. > > In this patch you do NOT add titles to the rel=vcs links, which means that > everything works fine only if there is a single URL for each project. If a > project has different URLs, it's going to appear multiple times as _different_ > projects to a spec-compliant reader. > > A possible solution would be to make @git_url_list into a map keyed by the > project name and having the description and repo URL(s) as values. > > Since there is the possibility of different projects having the same > description (e.g. the default one), the link title could be composed of > "$project - $description" rather than simply $description. > > Note that both in summary and in project list view you already retrieve the > description, so there are no additional disk hits. Wouldn't "$project git repository" (i.e. do not use description at all) be a simpler, faster and also _better_ solution? -- Jakub Narebski 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
