Fossil SCM
Unintuitive interpretation of p= and bt= query parameters on /timeline
ed62a4d35332595…
· opened 3 years ago
- Type
- Feature_Request
- Priority
- Immediate
- Severity
- Important
- Resolution
- Fixed
- Subsystem
- —
- Created
- March 24, 2023 1:04 p.m.
The p=X and bt=Y query parameters on /timeline are designed to show all ancestors of X back to Y. However, if Y is a tag that is on multiple check-ins, it selects the most recent Y over the entire span of check-ins, not the most recent Y that occurs prior to X. For example, the following URL does not work:
https://fossil-scm.org/home/timeline?p=bed4b0f7fc586f99&bt=release
The expectation is that the URL above would work the same as the following:
https://fossil-scm.org/home/timeline?p=bed4b0f7fc586f99&bt=487776dc454b2bb6
Comments (1)
The p=X and bt=Y query parameters on /timeline are designed to show all ancestors of X back to Y. However, if Y is a tag that is on multiple check-ins, it selects the most recent Y over the entire span of check-ins, not the most recent Y that occurs prior to X. For example, the following URL does not work:
https://fossil-scm.org/home/timeline?p=bed4b0f7fc586f99&bt=release
The expectation is that the URL above would work the same as the following:
https://fossil-scm.org/home/timeline?p=bed4b0f7fc586f99&bt=487776dc454b2bb6