Diff for "TutorialClone"

Differences between revisions 4 and 40 (spanning 36 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 4 as of 2005-08-26 01:22:31 → 
  Size: 1956
  Editor: waste
  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:
-== [Tutorial] - cloning a repository ==
+== Tutorial - Cloning a Repository ==
''(This page is part of the [[Tutorial]] series. Previous part is TutorialInit, next part is TutorialHistory)''
-Line 3:
+Line 4:
-We have followed TutorialInstall to install ["Mercurial"] already, right?  Good!
+You have followed TutorialInstall to install Mercurial already, right?  Good!
-Line 5:
+Line 6:
-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.
+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:
-The easiest way to get started with ["Mercurial"] is to use a ["Repository"] that already contains some files and some history.
+The easiest way to get started with Mercurial is to use a repository that already contains some files and some history.
-Line 9:
+Line 10:
-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.
+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.

Let's clone a small "hello, world" repository hosted at selenic.com:
-Line 12:
+Line 15:
- $ hg clone http://www.serpentine.com/hg/hello my-hello
+$ hg clone http://www.selenic.com/repo/hello my-hello
-Line 14:
+Line 17:
-['''Note''': sorry, but this isn't a real URL yet, because ["Mercurial"] doesn't yet allow you to ["Serve"] multiple repositories using a single daemon.  I'm working on a fix.] 

[Until this fix is in place, one can use
+If all goes well, the {{{clone}}} command prints this (Mercurial 1.4):
-Line 19:
+Line 20:
- $ hg clone http://selenic.com/hg my-hg-clone
+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
-Line 21:
+Line 28:
-to try things out whith an already working repository. WARNING, this repository is not the smallest thing out there.]

If all goes well, the {{{clone}}} command prints no output.  We should now find a directory called {{{my-hello}}} in our current directory:
+We should now find a directory called {{{my-hello}}} in our current directory:
-Line 26:
+Line 31:
- $ ls
 my-hello
+$ ls
my-hello
-Line 29:
+Line 34:
-Inside the {{{my-hello}}} directory, we'll find some files:
+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 32:
+Line 37:
- $ ls my-hello
 hello.c  Makefile
+$ ls -a
.  ..  .hg  Makefile  hello.c
-Line 35:
+Line 40:
-These files are exact copies of the files in the ["Repository"] we just ["Clone"]d.
+These files are exact copies of the files from the [[Tip|tip]] revision of the default branch in the repository we just cloned.
-Line 37:
+Line 42:
-'''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.
+'''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.
-Line 39:
+Line 44:
-At this point, we can start examining some of the history of our new ["Repository"], by continuing to TutorialHistory.
+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.

----
CategoryTutorial