Modify ↓
#1097 closed enhancement (duplicate)
Long views need paging - i.e. 'next', 'previous', X..X+N-1, X+N..X+2N-1, etc functionality
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | version control/log view | Version: | 0.8 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
I have experimental subversion repository which isn't even extremely large; however, it contains some 7500 revisions (and growing), and I'd _really_ like it if the reposition-level browse source→revision history would not dump all of it at once.
Default should be say, 100 at a time, although option for all should be of course available (as well as those standard 'next', 'previous', and number-oriented picking of those near (before/after the current active set)).
If I get desperate I'll write patch, but I'm not yet :-)
Attachments (0)
Change History (3)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Btw, this was already requested some time ago: see #426. It even suggests a default of 100 logs at a time, as above :)
comment:3 by , 20 years ago
| Component: | changeset view → log view |
|---|---|
| Description: | modified (diff) |
Note:
See TracTickets
for help on using tickets.
I agree. In addition, I think the log view should stop on copy by default. This would be very useful for browsing branch log views: one would see only what happened since that branch was created.
A check box Stop on copy could be unchecked in order to show the full history.