On December 27, 2019 6:58:11 PM GMT+01:00, Joseph Myers <j...@polyomino.org.uk> wrote: >On Fri, 27 Dec 2019, David Malcolm wrote: > >> What the plan for such branches? > >My view is: add all refs (and thus all objects) from the existing git >mirror to the converted repository, probably under names that are not >fetched by default (this increases the repository size, after git gc >--aggressive, from 1.4 GB to 1.7 GB). See the add-git-svn-history >script >in the gcc-conversion repository (which just runs a single git fetch >command). That would be in addition to keeping a renamed copy of the >existing mirror. > >People with active such branches might then create rebased versions (on > >top of the freshly converted history, and under new names).
Does this allow to keep the URL of the old git mirror and the new official fit repo the same or would that cause conflicts with existing clones? If that's not possible instructions how to manually import a branch (fetch refs from the old repo, rebase and push?) would work for me, too, and would allow me to only keep the single active branch. As far as I understand active branches require manual work anyway? Richard.
