Merge lp:~jameinel/loggerhead/merge_point_config into lp:loggerhead
Status: | Rejected |
---|---|
Rejected by: | John A Meinel |
Proposed branch: | lp:~jameinel/loggerhead/merge_point_config |
Merge into: | lp:loggerhead |
Diff against target: |
150 lines (+39/-11) 4 files modified
loggerhead/apps/branch.py (+8/-1) loggerhead/apps/transport.py (+8/-3) loggerhead/config.py (+10/-1) loggerhead/history.py (+13/-6) |
To merge this branch: | bzr merge lp:~jameinel/loggerhead/merge_point_config |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Matt Nordhoff | Needs Information | ||
Review via email: mp+24145@code.launchpad.net |
Description of the change
This adds a configuration option
--show-
--no-
and
http_
This changes the 'revision' view, and the view when you expand a revision in the 'changes' view.
This is moderately expensive to compute, and potentially *very* expensive to compute if we get rid of/change the cache infrastructure.
So this is a step along the way to turn expensive stuff into options you can turn off. I'm not sure how to document it, more than just the 'command-line' documentation.
Unmerged revisions
- 412. By John A Meinel
-
Turn show_merge_points into a config setting.
Today it doesn't cost a whole lot, but with the caching changes, it will
start to cost a bit more.
Chopping out features to improve performance makes me sad, but if you think it's the right call, I won't object. Besides, it defaults to leaving the features on.
Although it might be prudent to wait to land this until we're sure the caching changes will cause problems.
58 + show_merge_points = ui.bool_ from_string( show_merge_ points)
bool_from_string() was added in bzr 1.18, while Loggerhead is currently supposed to support...um, 1.13? I forget. Anyway, older than 1.18. In fact, another part of Loggerhead implements this function itself.
I'm not sure it's worth changing the backwards compatibility just for this, although it's kind of moot since we're probably going to kill everything before 2.0 by landing your other major changes.
78 + # XXX: Shouldn't this be registering an atexit hook to delete the
79 + # directory? Otherwise we fill up /tmp with caches that we won't
80 + # ever use again...
Personally, I always shut down Loggerhead in ways that don't trigger atexit hooks. :( (Ctrl+C or Py_FatalError because StaticTuple doesn't like OOMs.)