"bzr send" goes through too much history
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Fix Released
|
Wishlist
|
Jelmer Vernooij |
Bug Description
With bzr 1.17 and bzr-svn 0.6.4:
1. To work around bug 407283, add the following lines to your ~/.bazaar/
"
[13f79535-
use-cache = False
"
2. Then do bzr branch http://
3. Change a file in your branch and commit your change.
4. bzr send -o /dev/null
To perform the send, Bazaar says that it wants to do "discovering revprop revisions" for over 800k revisions.
Considering my branch only has 1100 revisions, I didn't expect it to have to go through more than that.
I don't really understand why it has to go through anything not in my local branch (which should be quick since it's on disk) or in new revisions in the upstream repository that haven't been merged yet. But that might be because I don't understand what send really has to do, so I don't know if that's fixable.
tags: | added: usability |
Changed in bzr-svn: | |
status: | Fix Committed → Fix Released |
assignee: | nobody → Jelmer Vernooij (jelmer) |
milestone: | none → 1.0.3 |
This is caused by the fact that you have disabled the cache.