Cloning Question

Martin Geisler mg at lazybytes.net
Thu Jan 7 12:27:45 CST 2010


"Josh Malinski" <JMalinski at anasazisoftware.com> writes:

Hi Josh

> I have been using Mercurial for some time now on local projects and
> have had good success however now I am running into an issue trying to
> implement it on a greater scale. I have a binary file that is over
> 100Mb in size (I know I shouldn't be tracking this size of a file but
> I am). When I clone the repository on another machine to its local
> disk everything runs just fine, however when I try to clone the
> repository to a disk that is stored on our filer the clone fails
> without any log message that I can find but when it fails it is on
> this 100Mb file. I am pretty sure that the problem isn't with
> Mercurial and the problem is with our filer but I need to have some
> sort of trail so that I can push back at our vendor. So with that
> being said is there a log or a mode of some sort that I can run the
> clone in to generate a log of some sort.

You can run 'hg --debug clone' to get more output. But I don't know if
that will tell you enough.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial/attachments/20100107/e529ff87/attachment.pgp>


More information about the Mercurial mailing list