On Thu, Nov 28, 2019 at 5:46 PM Joseph Myers <jos...@codesourcery.com> wrote: > > On Wed, 27 Nov 2019, Eric S. Raymond wrote: > > > Joseph Myers <jos...@codesourcery.com>: > > > One more observation on that: in my last test conversion, deleting the > > > emptycommit-* tags took over 7 hours (i.e. the bulk of the time for the > > > conversion was spent just deleting those tags). Deleting tags matching > > > /-root$/ took about half an hour. So I think there is a performance issue > > > somewhere with (some cases of) tag deletion by regexp, at least when the > > > regexp matches a large number of tags (but some other bulk deletions seem > > > to run much quicker per tag). Taking a few seconds per tag is fine for an > > > individual deletion, but a problem when you want to delete 4070 tags at > > > once. > > > > File that as an issue, please. Go has very good profiling tools, finding > > the hotspot(s) in situations like this is easy and thus we should be able to > > fix this quickly when it reaches the top of the priority list, > > https://gitlab.com/esr/reposurgeon/issues/169 filed for this performance > issue. > > https://gitlab.com/esr/reposurgeon/issues/170 filed for deleted branches > and tags wrongly reappearing in the conversion. > > https://gitlab.com/esr/gcc-conversion/merge_requests/17 filed for my > latest rearrangement of tag/branch deletions to help the review of which > we actually want to delete, commenting out those that ought not be > necessary any more (many of which then wrongly appear in the conversion > because of reposurgeon issue 170).
Can't branches and tags be deleted after the conversion as well? Richard. > -- > Joseph S. Myers > jos...@codesourcery.com
