Exactly :) Cool! Although it seems weird to me to have the revision in the middle of the URL.
This also works for tags and branches (or any 'ref' for that matter instead of the sha1)
Where would you want the revision? At the very end? Right now, it's associated with the repo, which makes sense and is easier on our URL routing. But I'm curious to hear what you'd prefer.
Actually on further thought maybe this does make more sense. I don't really have a strong preference either way anyway.
I think I agree with parent - if the premise is that the units we're dealing with are the functions, then I want to usually access `/function`, and `/function/revision` is being more specific.
I get what you're saying, but it seems like the URL mixes where you're coming from with where you want to take us.
I think it actually makes sense there, as a logical hierarchy: you want a given repository, at a given revision (e.g. a commit hash), and a given file within that revision.