Geek Answers Handbook

Folder structure in mercury repo?

I just switched from svn to mercurial and read some tutorials about this.
I still have some perplexities that I hope you could help me figure out.
I wonder if I understood the folder structure in the Mercurial repo rule.
In svn repo, I usually have the following folders:

IOS:

branches (branches/chat, branches/new_login etc)
tags (version1.0, version2.0 etc)
sandbox
trunk

Should a branch really be another clone of the original / central repo in the mercurial?
it seemed like when i read the manual.

And the tag is just a named identifier, but you have to clone the source / center repo when you want to create a tag?

How about a sandbox? should this be another clone?

So, you just have in the repo all the folders / files that you would have in the folder with the trunk?

mercury:

central repo: projects folders/files (not in any parentfolder)
tag repo: cloned from central repo at a given moment for release 
  (version1.0, version2.0 etc)
branch repo: cloned from central repo for adding features (chat, new_login etc)
sandbox repo: experimental repo (could be pushed to central repo, or just deleted)

?

+4
3

, DVCS, Mercurial ( Git).

Mercurial 4 ( SO ):

ConvertExtension ( )

SVN Mercurial , . SVO- Mercurial ( ), , , :

hg clone -r <branch-head-rev> <repo> <new-repo>
+4

, , , , .

/ mercurial?

, - , . , , "" "".

- , / , ?

- , . - " 0.8", , 0.8 427. , (, bugfix , 0.8, ). , , .

? ?

, "" - "- , ", . , , , .

, /, ?

, , "" .. Mercurial, , .

Mercurial Book? .

+4

mercurial: anonymous, clone, named ( ).

Depending on what you want to do (start parallel development of functions, experiment with the sandbox, etc.), you would choose one or the other. Mercurial alone does not impose any one method or workflow and simply provides you with selection mechanisms.

This article explains this much better. It helped me understand.

+1
source

More articles:


All Articles