Corrupt repositories

[Joshua Austin]

We have mercurial set up on a server where people can push/pull through a samba share with tortoise hg.
We are encountering issues with corrupt repositories where (this is the current theory) old versions of mercurial/tortoisehg were used to push changes.

I have read a faq on corruption, but that seems to cover more how one might be able to recover a corrupt repository.  There doesn't seem to be anything on things I can do to prevent the repository from getting corrupt to begin with.

Is there some config setting I can add to a repository that will not allow an old version to push to a repository?  Something to the effect of "Your version of mercurial is too old, please upgrade before pushing"?

Joshua Austin
Web Developer
CareTech Solutions
Office: (248) 823-0529
[cid:image001.png at 01CCB40E.B6B68AE0]<http://www.caretech.com/>
Helping extraordinary people do extraordinary things

Best in KLAS
Extensive IT Outsourcing
2008, 2009 & 2010
Top 20 Best in KLAS Awards
www.KLASresearch.com<http://www.klasresearch.com/>

[cid:image002.png at 01CCB40E.B6B68AE0]



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111206/2309462b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8511 bytes
Desc: image001.png
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111206/2309462b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2336 bytes
Desc: image002.png
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111206/2309462b/attachment-0001.png>