Merge lp:~nmb/brz/warn-bazaar-directory into lp:brz
Proposed by
Neil Martinsen-Burrell
Status: | Needs review |
---|---|
Proposed branch: | lp:~nmb/brz/warn-bazaar-directory |
Merge into: | lp:brz |
Diff against target: |
49 lines (+19/-3) 2 files modified
breezy/config.py (+16/-3) doc/en/release-notes/brz-3.0.txt (+3/-0) |
To merge this branch: | bzr merge lp:~nmb/brz/warn-bazaar-directory |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman | Needs Fixing | ||
Review via email: mp+325943@code.launchpad.net |
Description of the change
This prints a warning ONCE when the user is using the `.bazaar` configuration directory. Further uses of the directory are still logged to `.brz.log` as before. We could easily make that logging also happen only once if we would prefer less spam in that file.
To post a comment you must log in.
Unmerged revisions
- 6709. By Neil Martinsen-Burrell
-
Warn when using .bazaar configuration directory
There are two complicating factors here that this change does address:
* We don't want to do all the work to load config each time this function is called
* We still need a generic don't multiply warn for various things
As a concrete suggestion, I think a better choice is storing the config on global state rather than having a warning_printed attr, which will also happen to make any warning only appear once.
Is there any reason to refresh the config dir mid process execution?