Version control of really huge files

We're currently using perforce company wide, but I use git and git p4. I keep trying to convince people that perforce has a shitty workflow though, but the large file support is why it's still gotten a pass.

I don't have to do much with databases, but a lot with multimedia and large files for which you want some version control are rather common there. And it's more tricky because it's not text-based but binary and because you usually don't want every change to be a new version but only save very specific versions and otherwise changes should just replace the last version. Actually I haven't found yet a way to do that with mercurial which I use otherwise. So for now I just mix: Really large files are kept outside hg and saved and versioned by hand which means I have to distribute them additional to hg export when copying the project around. And for smaller files I just create new versions on each change even though I don't like it and would mostly prefer to just replace old versions. Unfortunately that is not the problem solved in this article.

What I would need would be a version control system that allows me to tag files so that those files are just replacing previous revisions on a commit (maybe still noting all the times they got updated) unless I specifically tag them as "new version".