mercurial

问题 I am using Tortoise-Hg for cloning a fork from CodePlex and cloning stops in the middle of the process . I have tried it more than 6 times and it does have a problem. I am using the visual client of Tortoise-Hg and I gave the source as https://hg.codeplex.com/forks/xxx/xxxx and selected a destination First used compressed method This is what appeared in the command prompt % hg clone --verbose -- https://hg.codeplex.com/forks/xxx/xxxx xxxx But the process start quite fast and then it get hung

问题 Is there any way I can enter a particular filename - e.g. "xyz.txt" - and search for any checkins of that file within a Mercurial repository using TortoiseHG? If not, why not? Isn't this what version control is for? 回答1: In the "Hg Repository Explorer" window choose the "File Patterns" filter in the combo box and type the name of the file (e.g., xyz.txt) in the field next to it and hit return. You would now see only the revisions where xyz.txt was modified. If you want to search your entire

问题 I'm thinking in git terms here ... is it possible to see how many local commits you have made ahead of the origin? As in git, if you type git status it will tell you Your branch is ahead of blah by blah blah Is there a similar thing in Mercurial? I know there is hg outgoing but I don't want a command that hits the server as I want to put the output in my prompt (like the commonly implemented bashrc funciton num_git_commits_ahead ) 回答1: I think hg summary --remote will give you what you want,

问题 Suppose I have several commits in local repo, and some uncommited changes in working dir. After hg pull , hg update , I get a couple of new changesets from central repo which create a new head in local repo. Now suppose, I don't want to merge those two heads and push, in which case I'll get the message that I have uncommited changes in working dir, when trying to merge. As well, suppose I don't want to use hg shelve in order to shelve uncommited changes and merge without problems, but would

问题 While trying to work out an integration between Kiln and Bamboo I ran into an issue that Fog Creek support indicated might be a problem of having too many topological heads in my repository. We typically have a pattern of closing a branch prior to merging back into a main branch but that clearly gets forgotten from time to time. $ hg head -t | grep ^changeset: | wc -l 1361 My understanding is that those heads need to be communicated one way or the other when pulling from the hosting Mercurial

问题 I would like to know why the following pattern is not possible. Having created a local feature branch (minor_feature - not intended to be shared with the world) I would like to rebase the work on it on to the tip of a well known branch (stable). However I have discovered that rebase finds nothing to be rebased in the case where stable has not progressed since branching away from it. I appreciate that this breaks the rule that the destination of rebase can not be an ancestor of the source but

问题 Goal and context I am writing a bash script (called foreach_repo ) that should execute the passed parameters as a shell command, e.g.: foreach_repo hg status should execute the command hg status . (It does this on a complicated nested structure of repositories, I have no control over this structure, but I need to batch operate on them quite often). This type of command is similar to sudo and other 'higher-order' commands; for example sudo hg status would in turn execute hg status with

问题 I may do development work for 2 weeks before one or two features get pushed to all the production servers, and since this is a Ruby on Rails project, many files can be modified. So using Mercurial as the source control, is there a good way to list all filenames that are modified (or added) by me, between the current version and revision 4822? (the number 4822 is before I do the first hg push , I do an hg out and see that the changeset that will go out is 4823, so I will diff with 4822)

问题 Recently, I've started experimenting with Mercurial, due to the fact that it always attracted it because of its simplicity and "just works" principle. Or at least, that's how others always described it. They also usually described it as "practically the same as git with just a few minor changes you won't notice" - only for me to discover it isn't quite so. I'm having problem with Hg branches. Pardon me if this is an overly simple question, but in git one has a working directory and a repo (

问题 This question already has answers here : Closed 7 years ago . Possible Duplicate: Generating a list of which files changed between hg versions hg diff -r 5 -r 10 will give the differences between revisions 5 and 10. But I want to see specifically just a list of files that are different - I don't want to see the full diffs. Is there a quick way to do this? 回答1: hg status can do this. The main purpose of hg status is showing modified files in the working directory (in comparison to the last