Mercurial Subrepos – How do you create them and how do they work?

by

You could probably try this stuff out and learn it more quickly than writing up your question took, but I’ll bite.

Can any or all of these steps be
executed with TortoiseHG, as of
version 0.9.2? If yes, how?

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. Use the command line to create and them and you’re good to go.

What does
the above code do (a line-by-line
explanation would be much
appreciated).

hg init main  # creates the main repo
cd main # enter the main repo
hg init nested # create the nested. internal repo
echo test > nested/foo # put the word test into the file foo in the nested repo
hg -R nested add nested/foo # do an add in the nested repo of file foo
echo nested = nested > .hgsub # put the string "nested = nested" into a file (in main) named .hgsub
hg add .hgsub # add the file .hgsub into the main repo

Here are some specific
questions that came to mind as I was
trying to decipher it: What does > do?

That has nothing to do with mercurial it’s standard shell (unix and dos) for “put the result into a file named X”

In line 5, I don’t
understand what nested/foo is. Where
did foo come from? What is foo? A
repository? A folder?

It’s a file in the subrepo. Foo is a traditional arbitrary name, and the arbitrary contents are the string “test”

Line 6 – this
one completely baffles me.

It’s putting the contents in .hgsub necessary to say that nested is a nested repo named nested and located at nested.

In line 7,
I assume .hgsub is being added to
main? Or is it being added to nested?

main

Let’s say I get my subrepos set up,
and my Bar repository is now up to
revision 10. If I attempt to update to
revision 7, will this cause my library
folders (My
Documents/Development/Libraries/ProjectA
and …/Libraries/ProjectB) to update
to whatever is stored in revision 7 as
well? Given that Foo also refers to
Libraries/ProjectA, this could get
interesting!

Revision numbers won’t carry across, but you have control by editing the .hgsubstate file.

More Related Contents:

  1. How to edit incorrect commit message in Mercurial? [duplicate]
  2. Mercurial for Beginners: The Definitive Practical Guide
  3. Named Branches vs Multiple Repositories
  4. Mercurial — revert back to old version and continue from there
  5. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  6. Mercurial: How to ignore changes to a tracked file
  7. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  8. Mercurial: Merging one file between branches in one repo
  9. What is the difference between hg forget and hg remove?
  10. When should you branch?
  11. Git and Mercurial – Compare and Contrast
  12. Using IPython / Jupyter Notebooks Under Version Control
  13. ClearCase advantages/disadvantages [closed]
  14. Should I store generated code in source control
  15. How and/or why is merging in Git better than in SVN?
  16. What is the cleverest use of source repository that you have ever seen?
  17. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  18. Source control vs. Revision Control?
  19. Git interoperability with a Mercurial Repository
  20. Why is branching and merging easier in Mercurial than in Subversion?
  21. Storing third-party libraries in source control
  22. how to ignore files in kiln/mercurial using tortoise hg “that are part of the repository”
  23. Is version control (ie. Subversion) applicable in document tracking? [closed]
  24. Can we finally move to DVCS in Corporate Software? Is SVN still a ‘must have’ for development? [closed]
  25. How do I perform a recursive checkout using ClearCase?
  26. Branching Strategies [closed]
  27. What makes merging in DVCS easy?
  28. Store password in TortoiseHg
  29. Handling renames: svn vs. git vs. mercurial
  30. What is the difference between all the different types of version control?

Leave a Comment