Service disruption: git converter currently down

[Ed Maste]

On Mon, 23 Sep 2019 at 13:51, Sean Chittenden <sean at chittenden.org> wrote:
>
> >
> > Please note however, that more "garbage" metadata escaped from SVN into
> > github, meaning 3rd parties have a hard time re-running the conversion and
> > making sure that it matches SVN down to the metadata (i.e. timestamps).
> >
> Discussion of a force-push to github has occurred a few times and been
> explicitly ruled out because most of our corporate citizens use github to
> integrate changes from FreeBSD.

Unfortunately it's not just a few instances of bogus metadata (commit
timestamps and authors), there are also a cases where the git
conversion misrepresents the operation performed and makes for
confusing history.

One example of this is r306097 / df422cbea30e. A file that had been
removed in head needed to be restored, and in SVN it was done by
copying from the stable/10 branch. The git converter interpreted that
as a merge, and then grafted the post-branch stable/10 history into
head as a result. That is why we have a bit over 9000 stable/10
commits showing up in 'git log origin/master'.