On Thu, Mar 27, 2008 at 4:56 PM, didier deshommes <<a href="mailto:dfdeshom@gmail.com">dfdeshom@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Vladimir Marek <Vladimir.Marek <at> Sun.COM> writes:<br>
><br>
</div><div class="Ih2E3d">> Hmm, I still don't see your point. You want to backup your data for the<br>
> case that someone unauthorised modifies your repository?<br>
<br>
</div>We want to be able to get a set of patches (in text format) that are extracted<br>
from the repo. Then we want to be able to do an "hg init" and reimport all<br>
patch sets in the same order. If we have multiple parents, this is not<br>
so straightforward.</blockquote><div> </div><div>I think you were pretty clear on the HOW, but it looks like everybody here is wondering about the WHY...<br><br>The best I can understand is that you would have a "clear text" view of the repo content in order to be able to analyse it, and be sure that nothing is hidden in it. And then you want to be able to reimport it under a clean empty mercurial repo to be sure that the view given by mercurial is the view used by mercurial.<br>
Said otherwise, you want to check the data managed by mercurial without relying on mercurial behaviour....<br><br>Does it make sens ?<br><br>-mathieu</div></div>