Overview
| Artifact ID: | b7a1aee92d65997bdffe243e5595652aee16c2c04ba5f3ba9e99ce98bb12c532 |
|---|---|
| Ticket: | ed62a4d35332595ac992655176a92a12dc50cc8c
Unintuitive interpretation of p= and bt= query parameters on /timeline |
| User & Date: | drh 2023-03-24 13:04:18 |
Changes
- foundin changed to: "2.22"
- icomment:
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>
- login: "drh"
- mimetype: "text/x-markdown"
- private_contact changed to: "5840dffc1663561cf96cb9eb1563447ad11d8bbe"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to:
Unintuitive interpretation of p= and bt= query parameters on /timeline
- type changed to: "Feature_Request"