Date: Sun, 15 Aug 2021 06:59:18 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257854] [NEW PORT] devel/reposurgeon: Repository surgeon Message-ID: <bug-257854-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257854 Bug ID: 257854 Summary: [NEW PORT] devel/reposurgeon: Repository surgeon Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: beyert@cs.ucr.edu Attachment #227211 text/plain mime type: Created attachment 227211 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D227211&action= =3Dedit devel_reposurgeon.shar (my apologies, I had a version of this port ready last year, but forgot to submit a PR, so this has been updated from version 4.24 to 4.28, accordingl= y) reposurgeon enables risky operations that version-control systems don't wan= t 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 r= epo 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 cleani= ng up cvs2svn conversion artifacts, dealing with nonstandard repository layout= s, 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, though that rate can fall significantly on extremely large repositories. File is attached (shar archive) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257854-7788>