I'm slowly becoming resigned to the fact that open-source community isn't going to convert to Perforce overnight... CVS is too well established as a standard. But I cringe at the thought of reverting back to CVS for my own OS projects. SO, I'm wondering if anyone has come up with an acceptable scheme for maintaining a public CVS repository with current "snapshots" from a private Perforce depot?

Obviously I could just treat each periodic update as a "vendor release" in CVS -- but then none of the change metadata would be available in the CVS repository. Any ideas?

-- Kaelin