Tortoisehg keeps saying hgsub changed how to#
How to find out what changeset of main repository contains specified changeset of subrepository.Use 'trivial' subrepo paths where possible.Use a thin shell repository to manage your subrepositories.
Note that the extra remove and commit steps are only required if the newly cloned repo has the same name of an already tracked directory. I was then able to either commit the main root repo, or the plugin1 repo independently.hgsub file and add the plugins/plugin1 = plugins/plugin1 line inside it. I created (or edited if the file already existed) a. The back again to the root of the main repo.Then I went back to my plugins/ directory, right click, TortoiseHg => Clone., I selected the http address of the plugin on bit bucket ( and clicked Done.I get back to the root of my repo, right click and Hg Commit.I first went to my plugins/ directory, right click on plugin1/, TortoiseHg => Remove Files.I also had those plugins online, hosted on BitBucket. I started with an existing repo, inside which I had a plugins/ directory filled with plugin1/, plugin/2 directories (not repositories, just simple directories). I'm using TortoiseHg on winXP, so I won't be able to tell you what hg calls were internally made, but I don't think anything fancy is used here. I've finally managed to make it work the way I'd love. Revision numbers won't carry across, but you have control by editing the. hgsub necessary to say that nested is a nested repo named nested and located at nested.
Foo is a traditional arbitrary name, and the arbitrary contents are the string "test" That has nothing to do with mercurial it's standard shell (unix and dos) for "put the result into a file named X" hgsub # put the string "nested = nested" into a file (in main) named. Hg -R nested add nested/foo # do an add in the nested repo of file fooĮcho nested = nested >. internal repoĮcho test > nested/foo # put the word test into the file foo in the nested repo Use the command line to create and them and you're good to go.Īppreciated). TortiseHG doesn't yet put GUI wrappers around sub-repo creation, but TortiseHG has always done a great job of working with the command line. You could probably try this stuff out and learn it more quickly than writing up your question took, but I'll bite. hgsubstate file in the main repository root." If a subrepo is included in the file list of a commit, the subrepo is committed along with the other changes, updating the.
When Mercurial considers a subrepo as dirty, it will appear in the commit tool as a special entry in the file list with a status of S. "TortoiseHg 1.0 introduced rudimentary support for subrepositories, and only in the commit / status tool.
Is this scenario not supported or am I doing something wrong? In Tortoisehg customer1\project1 is displayed with status S (subrepo)īut when commiting I get a message abort: customer1/project1: no match under directory! If modify the file Customer1\Project1\foo.txt and commit from the root it works >hg ci -m "command line commit"Ĭommitting subrepository customer1\project1 hgsub file under root looks like Customer1\Project1=Customer1\Project1 I have a directory structure like this: root I can't get Tortoisehg (1.0) to work with subrepos
0 kommentar(er)
