Merge lp:~jelmer/bzr/merge-distinguish-working-tree into lp:bzr
Proposed by
Jelmer Vernooij
Status: | Superseded |
---|---|
Proposed branch: | lp:~jelmer/bzr/merge-distinguish-working-tree |
Merge into: | lp:bzr |
Diff against target: |
130 lines (+25/-11) 3 files modified
bzrlib/merge.py (+16/-9) bzrlib/tests/test_merge.py (+5/-2) doc/en/release-notes/bzr-2.5.txt (+4/-0) |
To merge this branch: | bzr merge lp:~jelmer/bzr/merge-distinguish-working-tree |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman (community) | Needs Information | ||
Review via email: mp+87301@code.launchpad.net |
This proposal has been superseded by a proposal from 2012-01-03.
Description of the change
Properly distinguish the working tree (the tree to which we're going to be applying the found changes) from the this_tree in the merge.
This is required for some of the bzr-builddeb hooks I'm working on.
To post a comment you must log in.
Proposal should have <lp:~jelmer/bzr/propagate-other-branch> as a prerequisite?
Without seeing how this will be hooked up outside merge I'm not clear on how the parts will interact.
+ self.working_ tree.lock_ tree_write( ) add_cleanup( self.working_ tree.unlock) tree.lock_ read() tree.lock_ tree_write( )
operation. add_cleanup( self.this_ tree.unlock)
+ operation.
+ self.this_
- self.this_
Can working_tree and this_tree be the same location? If so this won't work.