WorkingTree.clone() doesn't support 'null:'
Bug #876423 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
High
|
Jelmer Vernooij | ||
Bug Description
various bzr-pipeline tests fail with bzr.dev at the moment, because WorkingTree.
I'm not sure if this is actually correct behaviour in bzr.dev; if you agree, please reassign to bzr.
Related branches
lp:~jelmer/bzr/workingtree-clone-null
- Martin Packman (community): Approve
-
Diff: 54 lines (+15/-1)3 files modifiedbzrlib/tests/per_workingtree/test_workingtree.py (+7/-0)
bzrlib/workingtree.py (+5/-1)
doc/en/release-notes/bzr-2.5.txt (+3/-0)
| affects: | bzr-pipeline → bzr |
| Changed in bzr: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| summary: |
- tests fail with bzr.dev + WorkingTree.clone() doesn't support 'null:' |
| Changed in bzr: | |
| status: | In Progress → Fix Released |
| milestone: | none → 2.5b3 |
To post a comment you must log in.
