You could write a browse rule for github, but, beyond that, there's not many assumptions you can make. - Ken On Thu, Nov 18, 2010 at 3:29 PM, Morgan Quigley wrote: > Right. It was convenient to make the "browse code" link work for SVN > repositories, since SVN uses HTTP and thus works for web browsers. I'm > not sure how to extend this concept for git. > > Thoughts from the git wizards out there? > > > > On Thu, Nov 18, 2010 at 3:13 PM, Eric Perko wrote: >> The browse code link is wrong for git repos on the package detail page. For >> example: >> http://www.ros.org/browse/details.php?name=kinect_node, click on Browse >> Code, and you get a link with a bunch of hudson stuff on it. >> Other packages have the same problem, such >> as http://www.ros.org/browse/details.php?name=cwru_nav or http://www.ros.org/browse/details.php?name=kinect_camera. >> Not sure how to link directly to a directory inside a git repo in all cases, >> but it definitely shouldn't have a /hudson/workspace/ on the end. >> GitHub definitely has no idea how to find that path :). >> - Eric >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> >> > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >