How should git-ubuntu handle user repository creation?

Asked by Robie Basak

In bug 2044575 it's suggested that git-ubuntu should pre-emptively fork repositories so that if a user pushes back to create a repository in their own namespace with near-identical history, it should be quick.

I was under the impression that Launchpad should automatically create a repository with data objects shared with the default repository target in this circumstance, so this should be unnecessary. However, empirically I have never seen the speed-up I expect if this were the case.

Please could you clarify how Launchpad behaves and/or is supposed to behave under these circumstances? Is there any automatic object sharing mechanism, and if so, how could git-ubuntu take advantage of it? Do you have any opinion on how git-ubuntu should implement this request please?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Clinton Fung Edit question
Last query:
Last reply:
Revision history for this message
Clinton Fung (clinton-fung) said :
#1

I'll have to have a dig to figure out if the capability you describe exists. I'm not aware of any such optimisation to share objects between repositories, and it feels like this would be quite complex (probably unnecessarily so) to implement.

Revision history for this message
Clinton Fung (clinton-fung) said :
#2

@Robie; can you share where you got the impression that there is automagic object sharing? This would be a good starting point for my investigation.

Revision history for this message
Dimitri John Ledkov (xnox) said :
#3

such object storage only existed in matching format bzr branches between project and personal branches for end-user visible pushes.
object storage is repacked and optimised server side, but to prevent initial push requiring one to transfer everything, one has to currently pre-fork the repo using the fork api.

Can you help with this problem?

Provide an answer of your own, or ask Robie Basak for more information if necessary.

To post a message you must log in.