Merge lp:~jameinel/bzr/2.5-merges-2.4 into lp:bzr/2.5
Proposed by
John A Meinel
Status: | Merged |
---|---|
Approved by: | John A Meinel |
Approved revision: | no longer in the source branch. |
Merged at revision: | 6515 |
Proposed branch: | lp:~jameinel/bzr/2.5-merges-2.4 |
Merge into: | lp:bzr/2.5 |
Diff against target: |
200 lines (+82/-19) 5 files modified
bzrlib/dirstate.py (+12/-3) bzrlib/tests/blackbox/test_uncommit.py (+17/-0) bzrlib/tests/per_workingtree/test_parents.py (+18/-3) bzrlib/tests/test_dirstate.py (+14/-2) doc/en/release-notes/bzr-2.4.txt (+21/-11) |
To merge this branch: | bzr merge lp:~jameinel/bzr/2.5-merges-2.4 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
bzr-core | Pending | ||
Review via email: mp+166489@code.launchpad.net |
Commit message
Merge 2.4 into 2.5, bringing in the fix for bug #855155 (Dirstate.
Description of the change
Just bringing in the last patches from 2.4.
2.4 now has the connection reset logic that 2.5 already had. So it involved a small amount of ignoring the 2.4 changes because the conflict needlessly. (It was backported, and then brought forward, and 2.5 has iterated into new changes since then, so 2.5 should be the canonical representation of the connection reset logic anyway.)
To post a comment you must log in.
sent to pqm by email