copy shamap as well when cloning/pulling

Bug #486570 reported by Russel Winder on 2009-11-22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar Git Plugin

Bug Description

Turning an email on the mailing list into a bug report as requested:

My original email:

"Updating the git map, as happens after taking a branch of a Bazaar
branch bound to a Git repository which is then bound to the same Git
repository and updated, takes ages. We cannot blame NFS and TDB here as
this is on the machine with the real discs locally. It has taken about
45mins to update the git map for 1749 revisions.

It gets worse :-( it then fetched 38 revisions and this took about 50

Jelmer responded:

"Please file a bug about this. We should probably get bzr to provide a
hook that can be used to copy the sha map when cloning a bzr branch."

Clearly further experiments are needed to get proper problem data . . .

Jelmer Vernooij (jelmer) wrote :

This requires bzrlib to provide a hook on repository clones/pulls first.

Changed in bzr-git:
status: New → Triaged
importance: Undecided → Wishlist
importance: Wishlist → Low
Jelmer Vernooij (jelmer) on 2009-12-15
Changed in bzr:
status: New → Triaged
importance: Undecided → Wishlist
status: Triaged → Confirmed
Jelmer Vernooij (jelmer) on 2010-03-15
summary: - updating the git map and pulling revisions takes a very long time
+ copy shamap as well when cloning/pulling
Jelmer Vernooij (jelmer) on 2011-02-04
tags: added: foreign hooks hpss
Jelmer Vernooij (jelmer) wrote :

Marking bzr bit as invalid - there's already a separate bug about that: bug 375736

Changed in bzr:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers