bisect does not drill down into merge commits
Bug #539937 reported by
SirVer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Bisect Plugin |
In Progress
|
Medium
|
Unassigned |
Bug Description
Bzr merge does not drill down into mergecommits that merged one branch into another. It is therefore only manually possible to detect errors in commits that came into the history via merging. This is a major downside of using bzr's bisect vs for example git's bisect.
Related branches
lp:~gthorslund/bzr-bisect/539937-subtree
- Jelmer Vernooij (community): Approve (code)
-
Diff: 578 lines (+129/-60)3 files modified__init__.py (+35/-35)
meta.py (+1/-1)
tests.py (+93/-24)
Changed in bzr-bisect: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in bzr-bisect: | |
assignee: | nobody → Gustaf Thorslund (gthorslund) |
Changed in bzr-bisect: | |
assignee: | Gustaf Thorslund (gthorslund) → nobody |
To post a comment you must log in.
I do not want to be pushy here, but a bisect plugin for a distributed version control system *must* support merge commits imho. Otherwise it is rather a bisect plugin for bzr-svn then for bzr. An importance of "Critical" would be more appropriate.