Originally created by: dcommander
This is another shortcoming of the new code viewer relative to ViewVC, and one that should be simple to address. When browsing the commits on a subversion repository, nowhere does it show you the revision number for the commit you are currently browsing-- although it does show you the parent and child revisions, if applicable.
Created #418 [#6284] Allura Code Viewer: show SVN revision in commit browser (2cp)
Related
Tickets:
#6284I'm not sure if we have to add revision numbers to commits on canvas or only to the current commit somewhere above the commit message?
It should go into the canvas, so that you can see all the revisions for all the commits, at a glance. Once it's there, I don't think we need to put it anywhere else.
Note this will affect git & hg too. Make sure you use the short-form of their commit ids.
Originally by: dcommander
Can you clarify what the canvas is, for those of us who are not Allura developers? This is a very simple issue. Go to the commit browser (say, https://sourceforge.net/p/libjpeg-turbo/code/commit_browser). Click on any commit. It shows the commit message in big blue text, but nowhere is the revision number shown. For maximum usability, it should really show the revision numbers both in the browser portion of the window (the top part) and in the big blue text area. That way, you could see the revision numbers at a glance, in case you needed to find a commit by number instead of by name, and you could also know for sure which revision number you're looking at currently.
The canvas is the part you referred to as "the browser portion" (it's rendered on an html
<canvas>
element).Originally by: dcommander
That makes sense. Yeah, if the rev. number is there, then you can tell which rev. you're looking at because it is highlighted, and thus it wouldn't be important for it to appear in the blue area.
Closed #418 [#6284] Allura Code Viewer: show SVN revision in commit browser, branch 42cc_6284
Related
Tickets:
#6284Made a few minor cosmetic changes which are on the master branch now. Also made a test update in the forgehg repo.
DRC: this will go live to SF.net in our next code push (probably this week)