Merge lp:~vila/bzr-svn/525571-minimal-atomic-write-bazaar-conf-files-2.1 into lp:bzr-svn/1.0
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 3326 | ||||
Proposed branch: | lp:~vila/bzr-svn/525571-minimal-atomic-write-bazaar-conf-files-2.1 | ||||
Merge into: | lp:bzr-svn/1.0 | ||||
Diff against target: |
42 lines (+10/-6) 2 files modified
NEWS (+3/-0) config.py (+7/-6) |
||||
To merge this branch: | bzr merge lp:~vila/bzr-svn/525571-minimal-atomic-write-bazaar-conf-files-2.1 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
bzr-svn developers | Pending | ||
Review via email: mp+29439@code.launchpad.net |
Commit message
Use atomic writes to protect config files against concurrent writers.
Description of the change
This patch should fix bug #525571 for lp.
https:/
won't land soon but https:/
The later is a minimal fix but needs to be done too in bzr-svn (which this patch does).
The former is a more correct/
The discussion I had with Jelmer that led to 3323 was based on a flawed design that didn't
require to use @needs_write_lock on set_user_option() methods (the correct design will break the backward compatibility for the 3323 fix :-/).
See the mp discussions mentioned above for the details, but in summary *this* patch:
- mimics the minimal fix landed in bzr-2.1,
- will fix the issue encountered on lp,
- doesn't require deploying a new bzr on lp,
- requires that a new bzr-svn is deployed on lp.