The git-filter-branch(1) manpage itself recommends git-filter-repo,
nowadays due to performance and safety problems.
It is impossible to completely expunge messages, even spam, as git
retains full history. Projects may (with adequate notice) cycle to new
It is impossible to completely expunge messages, even spam, as git
retains full history. Projects may (with adequate notice) cycle to new
-repositories/branches with history cleaned up via L<git-filter-branch(1)>.
+repositories/branches with history cleaned up via L<git-filter-repo(1)>
+or L<git-filter-branch(1)>.
This is up to the administrators.
=head1 COPYRIGHT
This is up to the administrators.
=head1 COPYRIGHT
$xurls{'grok-pull'} =
'https://git.kernel.org/pub/scm/utils/grokmirror/grokmirror.git' .
'/tree/man/grok-pull.1.rst';
$xurls{'grok-pull'} =
'https://git.kernel.org/pub/scm/utils/grokmirror/grokmirror.git' .
'/tree/man/grok-pull.1.rst';
+$xurls{'git-filter-repo(1)'} = 'https://github.com/newren/git-filter-repo'.
+ './blob/master/Documentation/git-filter-repo.txt';
$xurls{'ssoma(1)'} = 'https://ssoma.public-inbox.org/ssoma.txt';
$xurls{'cgitrc(5)'} = 'https://git.zx2c4.com/cgit/tree/cgitrc.5.txt';
$xurls{'ssoma(1)'} = 'https://ssoma.public-inbox.org/ssoma.txt';
$xurls{'cgitrc(5)'} = 'https://git.zx2c4.com/cgit/tree/cgitrc.5.txt';