Is it a good idea to track the same working copy with Git and SVN?

Question

Situation

Our client requires tracking only deliverables (PDFs of slides and documentation, source code) with Subversion/SVN, but we choose Git for internal developing purposes.

Research

With git-svn there is a tool to basically handle a SVN repository as a remote with Git. However I do not see the possibility to track all content with Git and only some versions of some content using SVN.

Question

Is it a good idea to use the two VCS on the same working copy to "develop" using Git and "release" finished deliverables to SVN? What obstacles may we encounter?

Tests

I have experimented with tracking the same working using the two version control systems and it works fine so far. I solved the issue of the two VCS tracking each other using ignores.

Answer 1

Certainly it's suboptimal to have two competing system for one task. But you stated the SVN is mandatory. And the alternative where only the SVN plays is way worse than the combo.

Using git (or other well-working VCS) to supplement a legacy one is common practice, we probably need to wait while the corporate dinosaurs die out along with their nonsense requirements.