Date: Tue, 22 Dec 2020 10:00:24 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@freebsd.org> To: Chris <bsd-lists@bsdforge.com> Cc: freebsd-git <freebsd-git@freebsd.org> Subject: Re: This may be a bit late in the game, but might this b any help? Message-ID: <X%2BG1qD1bPEeAxHkI@acme.spoerlein.net> In-Reply-To: <ca478c07776fc74afa906a4eb01cb646@bsdforge.com> References: <ca478c07776fc74afa906a4eb01cb646@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2020-12-21 at 13:27:02 -0800, Chris wrote: >Maybe others have already examined this[1]. I forgot I had a copy. > >eposurgeon - a repository surgeon > >reposurgeon enables risky operations that version-control systems don't >want to let you do, such as (a) editing past comments and metadata, >(b) excising commits, (c) coalescing commits, and (d) removing files >and subtrees from repo history. The original motivation for >reposurgeon was to clean up artifacts created by repository >conversions. > >reposurgeon is also useful for scripting very high-quality conversions >from Subversion. It is better than git-svn at tag lifting, >automatically cleaning up cvs2svn conversion artifacts, dealing with >nonstandard repository layouts, recognizing branch merges, handling >mixed-branch commits, and generally at coping with Subversion's many >odd corner cases. Normally Subversion repos should be analyzed at a >rate of upwards of ten thousand commits per minute. > >repodiffer is a program that reports differences between repository >histories. It uses a diff(1)-like algorithm to identify spans of >identical revisions, and to pick out revisions that have been >changed or deleted or inserted. It may be useful for comparing the >output of different repository-conversion tools in detail. > >Another auxiliary program, repopuller, assists in mirroring Subversion >repositories. Thanks, but that is a bit late, yeah. I've been working on the converter for the last 10 years ... I had another look at reposurgeon about a year ago and couldn't make heads or tails of it. A straightforward conversion worked, but re-produced all the cvs2svn non-sense, so I figure an elaborate ruleset would've been required anyway. Take a look at https://github.com/freebsd/git_conv/blob/master/freebsd-base.rules to get a sense of what is needed. Cheers Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X%2BG1qD1bPEeAxHkI>