Modify ↓
Opened 17 years ago
Last modified 9 years ago
#4760 new enhancement
"Newer revisions" link
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | next-major-releases |
| Component: | version control/log view | Version: | devel |
| Severity: | normal | Keywords: | navigation paging |
| Cc: | Ryan J Ollos | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
can we have a link "Newer revisions" (similar to "Older revisions") in the Revision log browser?
Thanks
Attachments (0)
Change History (8)
comment:1 by , 17 years ago
| Keywords: | navigation paging added |
|---|---|
| Milestone: | → 0.12 |
comment:2 by , 17 years ago
I'm not very familiar with python. if you tell me how to get the revision nomber of the newest revision, I can provide a patch.
comment:3 by , 17 years ago
ahh. I see the problem. in subdirs. still, could you tell me how to get the rev number of the HEAD, so I could have my local non-optimal solution? Thanks.
comment:4 by , 17 years ago
Look at the TracDev resources and, of course, at source:trunk/trac/versioncontrol/api.py (in particular, repos.youngest_rev gives you the latest revision).
See also #2053.
comment:6 by , 14 years ago
| Priority: | normal → lowest |
|---|
comment:7 by , 10 years ago
| Cc: | added |
|---|
comment:8 by , 9 years ago
| Owner: | removed |
|---|
Note:
See TracTickets
for help on using tickets.
That's actually problematic to achieve given the current implementation of the version control layer (and the general lack of support for "looking forward" given an arbitrary point the history, at least in the Subversion case).
In the future, we'll have a better cache system for the repository changes, and then I hope this should be possible.