Diff for "TutorialClone"

Differences between revisions 27 and 40 (spanning 13 versions)

Tutorial - Cloning a Repository

(This page is part of the Tutorial series. Previous part is TutorialInit, next part is TutorialHistory)

You have followed TutorialInstall to install Mercurial already, right? Good!

In Mercurial, we do all of our work inside a repository. A repository is a directory that contains all of the source files that we want to keep history of, along with complete histories of those source files (inside the .hg directory — see UnderstandingMercurial).

The easiest way to get started with Mercurial is to use a repository that already contains some files and some history.

To do this, we use the clone command.¹ This makes a clone of a repository; it makes a complete copy of another repository so that we will have our own local, private one to work in.

Let's clone a small "hello, world" repository hosted at selenic.com:

$ hg clone http://www.selenic.com/repo/hello my-hello

If all goes well, the clone command prints this (Mercurial 1.4):

requesting all changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
updating to branch default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved

We should now find a directory called my-hello in our current directory:

$ ls
my-hello

Inside the my-hello directory, we should find some files, together with the .hg directory, that contains Mercurial's private data (basically the history of the repository plus various state information — see Repository for more information):

$ ls -a
.  ..  .hg  Makefile  hello.c

These files are exact copies of the files from the tip revision of the default branch in the repository we just cloned.

Note: in Mercurial, each repository is self-contained. When you clone a repository, the new repository becomes an exact copy of the existing one at the time of the clone, but subsequent changes in either one will not show up in the other unless you explicitly transfer them, by either pulling or pushing.

By default, hg clone checks out (see update) the latest revision (usually referred to as the tip) of the repository's default branch into the repository's working directory. To see which revision is currently checked out, we can use the summary command:²

$ cd my-hello
$ hg summary
parent: 1:82e55d328c8c tip
 Create a makefile
branch: default
commit: (clean)
update: (current)

At this point, we can start examining some of the history of our new repository, by continuing to TutorialHistory.

CategoryTutorial

clone (1)
summary (2)

-  ⇤ ← Revision 27 as of 2009-11-22 16:03:53 → 
  Size: 2635
  Editor: Tovim
  Comment:
+   ← Revision 40 as of 2015-10-28 15:22:27 → ⇥
  Size: 2786
  Editor: alishamsulqamar
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-== Tutoriál - Klonování repozitáře ==
+== Tutorial - Cloning a Repository ==
''(This page is part of the [[Tutorial]] series. Previous part is TutorialInit, next part is TutorialHistory)''
-Line 3:
+Line 4:
-''(Toto je druhá část řady 1-9 [[Tutorial]]. Předchozí je[[TutorialInstall]], následuje [[TutorialHistory]])''
+You have followed TutorialInstall to install Mercurial already, right?  Good!
-Line 5:
+Line 6:
-Aplikaci Mercurial (nebo TortoiseHg) máme řádně nainstalovánu? Dobrá, popojedeme.
+In Mercurial, we do all of our work inside a [[Repository|repository]].  A repository is a directory that contains all of the source files that we want to keep history of, along with complete histories of those source files (inside the .hg directory — see UnderstandingMercurial).
-Line 7:
+Line 8:
-V Mercurialu se všechno důležité odehrává uvnitř [[Repository|repozitáře]]. Přísně vzato, repozitář je složka s označením {{{.hg}}}, umístěná spolu s pracovními (a dalšími) soubory uvnitř našeho pracovního adresáře. 
Nejjednodušší způsob jak začít s Mercurialem, je použít kopii projektu s již vytvořeným repozitářem.
+The easiest way to get started with Mercurial is to use a repository that already contains some files and some history.
 Line 10:
-Použijeme k tomu příkaz {{{clone}}}.<<FootNote(http://www.selenic.com/mercurial/hg.1.html#clone)>>  Ten vytvoří [[Clone|klon]] buď celého pracovního adresáře nebo jenom repozitáře, v závislosti na tvaru příkazu.
+To do this, we use the {{{clone}}} command.<<FootNote([[Cmd:clone]])>>  This makes a clone of a repository; it makes a complete copy of another repository so that we will have our own local, private one to work in.
 Line 12:
-Pořiďme si kopii nevelkého projektu, kterou uložíme do samočinně vytvořené složky mojeHalo na aktuálním disku:
+Let's clone a small "hello, world" repository hosted at selenic.com:
 Line 15:
-> hg clone http://www.selenic.com/repo/hello mojeHalo
+$ hg clone http://www.selenic.com/repo/hello my-hello
 Line 17:
-Půjde-li vše dobře, příkaz {{{clone}}} vytiskne toto (Mercurial 1.4):
+If all goes well, the {{{clone}}} command prints this (Mercurial 1.4):
-Line 29:
+Line 28:
-Na disku C:\ bychom nyní měli nalézt nový adresář {{{mojeHalo}}}, jehož obsah prozkoumáme otvíráním jednotlivých položek nebo příkazem:
{{{
> dir mojeHalo
}}}

Uvnitř adresáře {{{mojeHalo}}} nalezneme dva soubory `hello.c`}, `Makefile` a složku  `.hg`, která obsahuje historii repozitáře plus různé interní informace -- více viz[[Repository]]. 

Tyto soubory jsou přesnou kopií souborů z poslední ([[Tip|tip]]) revize původní větve klonovaného repozitáře.<<br>>
Informace o kopírované verzi repozitáře získáme příkazem[[Parent|parents]] :<<FootNote(http://www.selenic.com/mercurial/hg.1.html#parents)>>
+We should now find a directory called {{{my-hello}}} in our current directory:
-Line 41:
+Line 31:
-> cd mojeHalo
> hg parents
changeset:   1:82e55d328c8c
tag:         tip
user:        mpm@selenic.com
date:        Fri Aug 26 01:21:28 2005 -0700
summary:     Create a makefile
+$ ls
my-hello
-Line 49:
+Line 34:
+Inside the {{{my-hello}}} directory, we should find some files, together with the .hg directory, that contains Mercurial's private data (basically the history of the repository plus various state information — see [[Repository]] for more information):
-Line 50:
+Line 36:
-'''Note:''' V okamžiku provedeného klonování jsou oba repozitáře totožné. Později se zřejmě oba repozitáře nezávisle na sobě různě změní. Změny lze z jednoho repozitáře do druhého přenést přikazy
[[Pull|pull]] nebo [[Push|push]] -- viz dále.
+{{{
$ ls -a
.  ..  .hg  Makefile  hello.c
}}}
These files are exact copies of the files from the [[Tip|tip]] revision of the default branch in the repository we just cloned.
-Line 53:
+Line 42:
-Nyní se již můžeme pustit do zkoumání historie našeho nového repozitáře na další stránce -- TutorialHistory.
+'''Note:''' in Mercurial, each repository is self-contained.  When you clone a repository, the new repository becomes an exact copy of the existing one at the time of the clone, but subsequent changes in either one ''will not show up'' in the other unless you explicitly transfer them, by either pulling or pushing.

By default, `hg clone` checks out (see Cmd:update) the latest [[Revision|revision]] (usually referred to as the tip) of the repository's ''default branch'' into the repository's [[WorkingDirectory|working directory]]. To see which revision is currently checked out, we can use the summary command:<<FootNote([[Cmd:summary]])>>

{{{
$ cd my-hello
$ hg summary
parent: 1:82e55d328c8c tip
 Create a makefile
branch: default
commit: (clean)
update: (current)
}}}
At this point, we can start examining some of the history of our new repository, by continuing to TutorialHistory.