Tortoisehg global ignore verification#

Make scmid the authoritative revision, since revisions are ambiguous to a DVCS Issue #3567 might be tangentially related to this.ĭownload all files mercurial_scmid_authoritative.patch (2.89 KB) mercurial_scmid_authoritative.patch This is probably the sanest path to take with Redmine, in terms of keeping old URLs functioning and also to more or less parallel the way that Git repos are managed.

(as hgweb allows entering tags as well - I dunno if you want to get that elaborate :).

So the following URLs will bring up the same patch: However it allows entering a revision ID into the URL as well. The behavior of hgweb.cgi (the web frontend that comes with Mercurial) is to expose only the short-form changeset IDs. Do not use them to talk about changesets with other people. Revision numbers referring to changesets are very likely to be different in another copy of a repository. You should always use some form of changeset ID rather than the local revision number when discussing revisions with other Mercurial users as they may have different revision numbering on their system. While this does work, it's explicitly discouraged in Mercurial's documentation.

This documentation on certificates may help, as well.Redmine exposes Mercurial's revision IDs (one-up decimal number, similar to Subversion) as the primary means of referring to changesets, rather than the changeset ID (strings of hex digits, like Git).

Tortoisehg global ignore verification#

This should skip actual verification of the certificate because you are declaring that you already trust the certificate. 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. (check hostfingerprints or web.cacerts config setting)Ī better option, however, is host fingerprints, which are used by both hg and TortoiseHg. 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 That's machine-level config for TortoiseHg, but it doesn't seem to affect the Clone window. When you turn that on, it adds something like this to your mercurial.ini: That will bring up the Security window, where you can select the option No host validation, but still encrypted, among other settings. 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: