![]() Note that readtimeout is the timeout for inter-process communication, so it has nothing to do with the time required for pull processing. If it doesnt, there may be dust in the interprocess communication. This documentation on certificates may help, as well. If this helps, I think the hg process is stalled for some reason. This is a shelve extension bundled with tortoisehg. hgrc (or mercurial.ini for windows users): extensions. This should skip actual verification of the certificate because you are declaring that you already trust the certificate. No need to feel silly any more, just add this in. The Query button retrieves the fingerprint of the host's certificate and stores it in mercurial.ini: ī = 81:2b:08:90:dc:d3:71:ee:e0:7c:b4:75:ce:9b:6c:48:94:56:a1:fe In TortoiseHg's Security window, above No host validation is the option Verify with stored host fingerprint. ![]() ![]() hg/hgrc): extensions shelve Or if you are using TortoiseHg, you can easily enable the extension in the settings dialog. (check hostfingerprints or web.cacerts config setting)Ī better option, however, is host fingerprints, which are used by both hg and TortoiseHg. To turn it on, you need the following lines in your mercurial.ini file (or to enable it in just a single repository, add them to. This will spit out a number of warnings about not verifying the certificate, and will also show you the host fingerprint in each message, like the example warning below (formatted from the original for readability): warning: certificate with fingerprintĢ4:9c:45:8b:9c:aa:ba:55:4e:01:6d:58:ff:e4:28:7d:2a:14:ae:3b not verified On the command-line, you can use -insecure to skip verifying certificates: hg clone -insecure repository-clone Revision Sets We have replaced the filter bar of the Repository Explorer with a revision set bar in the Workbench. That's machine-level config for TortoiseHg, but it doesn't seem to affect the Clone window. TortoiseHg 2.0 includes a new shelve tool which is capable of moving changes between your working directory, a shelf file, or an unapplied MQ patch. When you turn that on, it adds something like this to your mercurial.ini: To restore these changes to the working directory, using 'hg unshelve' this will work even if you switch to a different commit. That will bring up the Security window, where you can select the option No host validation, but still encrypted, among other settings. Shelving takes files that 'hg status' reports as not clean, saves the modifications to a bundle (a shelved change), and reverts the files so that their state in the working directory becomes clean. In the TortoiseHG Workbench, in the Sync tab (or in the Sync screen), if you have a remote path selected, you should see a button with a lock icon on it:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |