Modify ↓
Opened 14 years ago
Closed 14 years ago
#9110 closed defect (fixed)
display of eligible changesets is broken when source newer than target
| Reported by: | Christian Boos | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | high | Milestone: | 0.12 |
| Component: | version control/changeset view | Version: | 0.12dev |
| Severity: | major | Keywords: | svn svnmerge mergeinfo |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When the most recent change was made on a branch which is a merge source for some target branch, the eligible changesets shown for that target branch won't contain the newer changeset.
Example: now just committed r9326 on branches/0.11-stable@9326, which doesn't show in trunk@9326, as the most recent change on trunk is only r9325.
Another unwanted effect is that the path info will show source: trunk @ 9325 even when r9326 was specified.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
Regression was introduced by r9125.
The initial fix r8310 for this issue was ported from 0.11-stable to trunk in r8315, but when merging the latter into MultiRepos in r8376, the change in browser.py (and only this one) was lost.