On Thu, Jan 15, 2009 at 11:04:35AM +0100, Johan Sørensen wrote: > > On Thu, Jan 15, 2009 at 10:53 AM, Sébastien Mazy <[email protected]> wrote: > >> It is rendering the tree of the head commit of that particular branch. > >> The reason it redirects to the commit sha and not the branch name is > >> that rails doesn't support multiple wildcard paths (eg > >> slashed_path/another_slashed_path) since it tell them apart easily. > >> Hence we use the commit sha of the tip commit in that particular > >> branch. > > > > And isn't it possible to get round this limitation of Rails? (just > > asking, never wrote anything using Rails or even Ruby) > > > > I see 2 problems in the current behaviour: > > - nitpicking: the URIs are not consistent depending on whether you're on > > a subdirectory branch (trees/mybranch vs tress/commit_number) > > - more annoying: I can't point someone at the tip of a subdirectory > > branch in gitorious, just to a commit that was once it > > Both valid points. I think the best we can do right now is to > urlencode the slash ("foo/bar" => "foo%2Fbar") but that's kinda ugly > too. > > I'm sure someone must have a better idea?
IMHO, it's not that ugly. That would be one easy way to make a difference between: - show me 'file' on the tip of the branch 'foo/bar': .../trees/foo%2Fbar/file - show me 'bar/file' on the tip of the branch 'foo': .../trees/foo/bar/file Otherwise, a bigger change in the building of URIs would be needed (probably with parameters, which you might think way more uglier?). -- Sébastien Mazy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
