On 14/02/15 05:28, Colin Watson wrote:
> When trying to implement William's suggestion, I found that indeed it's quite reasonable for Launchpad to take care of creating a GitRepository row when asked to translate-for-writing a well-formed path it doesn't know about yet, but it's still useful for turnip to deal with the "git init" bit when trying to receive into a repository path that doesn't yet exist on disk. This makes the interface between Launchpad and turnip much simpler when creating repositories.
>
> I've amended this branch with this new approach.
Will that still be useful when 99% of created repositories want to be
forks of existing ones, rather than fresh inits?
On 14/02/15 05:28, Colin Watson wrote: for-writing a well-formed path it doesn't know about yet, but it's still useful for turnip to deal with the "git init" bit when trying to receive into a repository path that doesn't yet exist on disk. This makes the interface between Launchpad and turnip much simpler when creating repositories.
> When trying to implement William's suggestion, I found that indeed it's quite reasonable for Launchpad to take care of creating a GitRepository row when asked to translate-
>
> I've amended this branch with this new approach.
Will that still be useful when 99% of created repositories want to be
forks of existing ones, rather than fresh inits?