We could simplify things, and assume that remote name is _never_
hierarchical, so that remote branches names are:
remotes/<remote>/<branch>
where <remote> does not contain '/'.
Additional problem is for "summary" view: should we limit number of heads
per remote, should we sort heads inside remote, or should we also sort
remotes, or should we sort remotes by time without grouping into repos?
--
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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
Re: Show remote branches on gitweb, Jakub Narebski, (Tue Nov 28, 11:14 am)