Bazaar should have a cache for downloaded revisions
Bug #328088 reported by
Nicholas Allen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
| Breezy |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When Bazaar fetches a revison from a remote location it should record this revision in a cache (which could have a configurable size). The next time it needs that revision it would not need to download it but would take it from the cache instead. This would simplify the use case where the user branches remotely without creating a shared repository. The next time they branch from the remote location it would happen much faster.
Revision history for this message
| Wesley J. Landaker (wjl) wrote | #1 |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: ui3 |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy ui3 |
| Changed in brz: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
This could also help in the multiple "bzr missing" case, or the "bzr pull" after "bzr missing" case.