Closed
Bug 506945
Opened 16 years ago
Closed 16 years ago
MXR should give VCS URL(s) for the browsed code
Categories
(Webtools Graveyard :: MXR, enhancement)
Webtools Graveyard
MXR
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: naesten, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061212 Iceweasel/3.0.11 (Debian-3.0.11-1)
Build Identifier:
It would be really handy if MXR would list the VCS URL(s) that correspond with the code or directory shown; in cases where files within a branch don't actually have URLs of their own, it should display the VCS URL for the branch and the path to the file within the version-controlled tree.
Reproducible: Sometimes
Steps to Reproduce:
1. Look at some code in MXR
2. decide it looks interesting and that you'd like to check it out
3. wonder where to check it out from
Actual Results:
I don't know where to check it out from.
Expected Results:
Was hoping for an SVN URL or something ...
http://mxr.mozilla.org/js/source/js/narcissus/js.js
you'll see "cvs blame", that means the file is managed in cvs which means you can load:
http://mxr.mozilla.org/js/source/js/narcissus/CVS/
and get the other bits you need....
but really, the fact that you see:
changes to
this directory
in the last: day
week
month
in a directory listing means that it is CVS managed and does effectively tell you the information you need.
this is a branched version of bugzilla:
http://mxr-test.konigsberg.mozilla.org/bugzilla3.0/source/
and those links are to:
http://bonsai.mozilla.org/cvsquery.cgi?branch=BUGZILLA-3_0-BRANCH&dir=mozilla/webtools/bugzilla&date=day
which shows that it actually does pull the tag information too.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•16 years ago
|
||
Darnit! Sorry, I somehow missed those boxes on the right. I was looking above and below the file contents ...
Updated•5 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•