Question on work-flow for big binary files

[Marcus Lindblom]

Hi,

I've mostly used Subversion before, but decided to try to switch to 
Mercurial at my new job. (I do have that leverage, yay. :)

It seems to be no big problem in using Mercurial to manage sources, but 
there's also the matter of content files (3d-models, textures, whatnot) 
that have a different characteristics/usage patterns than source code:

  * are big (10-100:s of megabytes)
  * change in bursts (a few weeks with 1-4 commits/day), then are stable 
for a long time (so some near-time rollback is necessary, but ancient 
history is not important)
  * are often binary

With svn, I could imagine a scheme where you'd store content-files in a 
separate repo which was processed (dumped/filtered/restored) every week 
or so to remove any intermediate copies above a certain age, of course 
keeping heads of any tags and branches.

Is something similar possible with Mercurial, or are there other tools 
out there which are better suited for this task?

Thanks!
/Marcus