in git, what ways are there to "lose" a commit in a way that you CAN'T recover using the reflog (so that you need to iterate over every single commit in the repository if you want to find it?

The only ways I know (using git's normal tools) are:

* using `git stash drop` or `git stash pop` to drop a stashed commit
* waiting 90+ days to try to recover the commit (so that it expires from the reflog)
* explicitly deleting the reflog in some way (rm -rf .git, git reflog expire, etc)

@b0rk history rewrite shenanigans, like squashing or dropping commits during a rebase
@DerPumu those should be recoverable with the reflog I think? If they're not I'd be interested to know why not!
@b0rk yeah you're right they should be