tortoisehg

In Git - with it's immutable changeset objects and mutable refs - I know that the original commits remain, which gives me a warm fuzzy feeling after an 'oops' "history rewriting" moment. For example, after a "history rewriting" git rebase the original changesets (cbe7698, 09c6268) are still there and a new changeset (08832c0) was added. I can easily restore/access the other changesets until such a time as they are pruned. $ git log --oneline --graph --decorate $(git rev-list -g --all) * 08832c0 (HEAD -> master) Added bar and quxx to foo.txt | * cbe7698 Added quxx to foo.txt | * 09c6268 Added

I am trying to get mercurial to run in a shell from my C# wpf application. My purpose is to retrieve the output into a string so that I can parse it. Unfortunately for me, it seems that hg.exe (from tortoiseHg), does not return anything via the code below. Other .exe's appear to work, as seen in the comments below; My Code is below; ` string workingDir = ""; string filename = ""; string param = ""; //This works workingDir = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location); filename = "unrar.exe"; param = ""; //this works workingDir = "c:\\program

背景 当有几十个仓库时，半年/1年要重新安装系统，就一直存在这个问题，每个仓库要重新注册，分散在很多的文件夹中，不好找。 版本信息 TortoiseHg4.5.3/4.0.1 @Windows 2016/2012 仓库注册表等信息位于，重装系统时可备份： C:\Users\Administrator\AppData\Roaming\TortoiseHg C:\Users\Administrator\AppData\Roaming\TortoiseHg>dir 驱动器 C 中的卷是 w2016@128gSSD 卷的序列号是 56B9-F633 C:\Users\Administrator\AppData\Roaming\TortoiseHg 的目录 2018/05/28 16:07 <DIR> . 2018/05/28 16:07 <DIR> .. 2018/05/28 15:28 2,802 OverlayServerLog.txt 2018/05/26 11:31 143 OverlayServerLog.txt.old 2018/05/28 16:07 6,718 thg-reporegistry.xml 2018/05/28 16:07 23,954 TortoiseHgQt.ini 4 个文件 33,617 字节 2 个目录 13,912,735,744 可用字节 方法

I am using TortoiseHg Workbench 64bit 2.1.4, though it may be an issue with Mercurial. The OS is Windows 7 (64bit). I have two projects that I push to two different locations (one is bitbucket, the other is an private one). They use different usernames and passwords, and I push over HTTPS. I have setup the keyring in my mercurial.ini: [extensions] mercurial_keyring= and in the two .hg/hgrc files, I have setup paths with their respective values: [paths] default = https://userX@domainX/XXX If I only work on one repo, the password is remembered each time I connect. However, when I switch between

I have a "main" repository, I clone it and make some changes in the clone. In the meantime, there are other changes in "main", so I pull them and merge them in my clone. I make more changes in the clone, and merge any other new changes from "main". This gives me this graph: When I finish my work in the clone, I push to the main repository and now the graph in "main" looks like this: I know they're topologically the same, but to me the first one is clearer (this one is a very simple case, but things could get more complicated). Is there any way to prevent this? I've found this question about

I'm using TortoiseHG with mercurial and I have to log my changes from last month. It has to be something like this in GIT: git log --since="2015-03-01" -p --author='me' > C:\history_3.log Can you tell me how can I do it (using tortoise gui or terminal)? You want to make use of mercurial's revsets, a very powerful language to filter the revisions listed: hg log -r"author('YOURNAME') and date('>2015-03-01')" or alternatively for the last 30 days: hg log -r"author('YOURNAME') and date('-30')" . See hg help revsets and hg help dates . EDIT: Using tortoiseHG, you can use the magnifying glass icon

问题 % hg add -- pll3.inc pll3.vhd pll3_inst.vhd pllClock.vhd waiting for lock on working directory of X:\woks\2017\proj\FPGAFW @proj held by '' 解决方法 关闭TortoiseHg后，删除这个文件： .hg/wlock 版本 TortoiseHg: 4.5.3 it should be : delete the file .hg/wlock 参考 https://codeyarns.com/2011/01/20/mercurial-waiting-for-lock-2/#comment-65155 Problem Mercurial repositories can sometimes be left in a locked state. A lock is created whenever a client is connected to a repository. But, this lock is not removed if the client got disconnected, say over the network. If any client now tries to change the repository (say