ability to store git cache in git repository
Bug #931995 reported by
jugglefish
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar Git Plugin |
Triaged
|
Wishlist
|
Unassigned | ||
| Breezy |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
when using 'git fetch bzr::' some mapping information seems to be saved inside the bzr branch in directory .bzr/git. It would be nice if this information could be kept inside the git repository as connecting to another branch could benefit from this information.
To cope with problems on large reps I am using the following workflow with perform subsequent calls like
* bzr pull -rX lp:hosted-rep /tmp/temp-branch
* cd to git rep
* git fetch bzr::temp-branch
If I now delete temp-branch and connect to lp:hosted-rep all this mapping information seems to be lost and has to be recalculated which is a dramatic performance penalty.
| Changed in bzr-git: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| summary: |
- git bzr:: mapping revisions ids + regenerates objects for some bzr->git operations |
| summary: |
- regenerates objects for some bzr->git operations + regenerates objects unnecessarily for some bzr->git operations |
| tags: | added: git-remote-bzr |
| Changed in bzr-git: | |
| importance: | Medium → Wishlist |
| summary: |
- regenerates objects unnecessarily for some bzr->git operations + ability to store git cache in git repository |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in brz-git: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| no longer affects: | brz-git |
| tags: | added: git git-remote-helper |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
This is mainly done this way at the moment because it makes sense when working in the bzr branch and interoperating with git.
For the other way around (with git-remote-bzr) I agree it makes sense to store the cache in the git repository.
That said, it seems a bit odd to store the cache for bzr data that isn't actually present in the git repository there.