Brett Randall

This is a fairly unusual requirement and usage-pattern for Git. It is not typical to want to regularly discard all or most of your source-code history based on its age....

``` java -jar bfg.jar --strip-blobs-bigger-than 100M [email protected]:abrhambas01/blacktrail-backup.git ``` See https://rtyley.github.io/bfg-repo-cleaner/#usage . After mirror cloning, BFG works on local repo `blacktrail-backup.git`.

You haven't used the `massive-non-file-objects-sized-up-to` option, which is designed to help with that. Try running with e.g. `--massive-non-file-objects-sized-up-to 20M`.

That's odd. Have you reviewed to report file output, or only `stdout`/`stderr`?

Which version of BFG are you running? Are you certain files were deleted in your run? You should see something like this in stdout/stderr: ``` Deleted files ------------- Filename Git...

Probably good to start out with stating BFG version, the command you ran and better still a sample repo. Note also that BFG can currently only delete according to name...

OK, `--delete-folders`, that makes sense. Currently the code cleans folders/trees (as opposed to files) by filter-to-retain, i.e. keep everything but what you asked to be deleted. In that way the...

Please post all commands you ran, starting from when you cloned the remote repo.

This doesn't show how you cloned your repo (or is it local only), whether you ran a `git gc` after or any follow up commands.

Related: #139 #293 #140 .