2

Is it possible to configure Mercurial or TortoiseHG to always use uncompressed transfer when pulling or cloning from certain servers? We have repositories on Kiln that have sub-repositories located on the local LAN (mostly large binary files). When cloning or pulling from Kiln uncompressed should NOT be used, however the sub-repositories SHOULD use uncompressed. I would like to specify that any time HG hits up our local server, it should use uncompressed. We are using HgLab as our local repository server.

Dave Nay
  • 549
  • 5
  • 23

2 Answers2

2

HgLab author here. Mercurial does not support --uncompressed flags for pulls. It's only supported for initial clones.

As a sidenote: I'll be releasing HgLab 0.3.10 later this week, and pulls are much faster now (up to 20x increase).

Update 8 months later. HgLab now has a way to enforce streaming clones.

Anton Gogolev
  • 113,561
  • 39
  • 200
  • 288
0

Are you accessing the local servers via SSH? If so, mercurial already disables compression (and you should also presumably disable compression in your ssh client). According to hg help urls:

Mercurial doesn't use its own compression via SSH; the right thing to do is to configure it in your ~/.ssh/config, e.g.:

Host *.mylocalnetwork.example.com
  Compression no   
Host *
  Compression yes
alexis
  • 48,685
  • 16
  • 101
  • 161