Differences between revisions 1 and 35 (spanning 34 versions)
⇤ ← Revision 1 as of 2005-08-26 00:58:28 →
Size: 2091
Editor: waste
Comment:
← Revision 35 as of 2008-02-12 20:20:01 → ⇥
Size: 2427
Editor: WagnerBruna
Comment: link to Brazilian Portuguese translation
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
(you might first want to read UnderstandingMercurial)
Line 3: Line 5:
This tutorial is an introduction to using ["Mercurial"]. We don't assume any particular background in using ["SCM"] software.
This tutorial is also available in French, following ["FrenchTutorial"] and in Spanish, following ["SpanishTutorial"].		 ''(Translations:
[:ChineseTutorial:Chinese],
[:FrenchTutorial:French],
[:GermanTutorial:German],
[:ItalianTutorial:Italian],
[:JapaneseTutorial:Japanese],
[:KoreanTutorial:Korean],
[:BrazilianPortugueseTutorial:Brazilian Portuguese],
[:SpanishTutorial:Spanish]
)''

This tutorial is an introduction to using Mercurial. We don't assume any particular background in using ["SCM"] software.
Line 7: Line 19:
 * The basic concepts and commands you'll need to use ["Mercurial"]
 * How to use ["Mercurial"] in simple ways to contribute to a software project		  * The basic concepts and commands you'll need to use Mercurial
 * How to use Mercurial in simple ways to contribute to a software project
Line 10: Line 22:
It is also strongly recommended that you have a look at the Mercurial man pages hg(1) and hgrc(5) which are in the source tree as doc/hg.1.txt and doc/hgrc.5.txt It is also strongly recommended that you have a look at the Mercurial man pages [http://www.selenic.com/mercurial/hg.1.html hg(1)] and [http://www.selenic.com/mercurial/hgrc.5.html hgrc(5)], which are in the source tree as {{{doc/hg.1.txt}}} and {{{doc/hgrc.5.txt}}}.
Line 14: Line 26:
The formatting convention is simple. Command names and parameters are displayed in ''fixed font''. The formatting convention is simple. Command names and parameters are displayed in {{{fixed font}}}.
Line 16: Line 28:
A line of input that you should type into your shell or command prompt is displayed in a fixed font, and the line will start with a ''$'' character. A line of input that you should type into your shell or command prompt is displayed in a fixed font, and the line will start with a {{{$}}} character.
Line 18: Line 30:
A line of output that you should expect ["Mercurial"] or your shell to display is displayed in a fixed font, but with no special character at the start of the line. A line of output that you should expect Mercurial or your shell to display is displayed in a fixed font, but with no special character at the start of the line.
Line 21: Line 33:
 $ this is a line of user input
 this is a line of program output		 $ this is a line of user input
this is a line of program output
Line 25: Line 37:
We use the ''bash'' shell in all examples. The concepts remain the same for other Unix shells and the Windows ''command.exe'', but the syntax of some operations may change. For example, ''ls'' in a unix shell is roughly equivalent to ''dir'' under MS Windows, and unix ''cat'' is similar to MS Windows ''type''. We use the {{{bash}}} shell in all examples. The concepts remain the same for other Unix shells and the Windows {{{cmd.exe}}}, but the syntax of some operations may change. For example, {{{ls}}} in a Unix shell is roughly equivalent to {{{dir}}} under Windows, and Unix {{{vi}}} is similar to Windows {{{edit}}}.
Line 29: Line 41:
 * TutorialInstall - installing ["Mercurial"]
 * TutorialClone - making a copy of an existing ["Repository"]
 * TutorialHistory - navigating the history of a ["Repository"]		  * TutorialInstall - installing Mercurial
 * TutorialClone - making a copy of an existing [:Repository:repository]
 * TutorialHistory - navigating the history of a repository
Line 33: Line 45:
 * TutorialShareChange - sharing changes with another ["Repository"]  * TutorialShareChange - sharing changes with another repository
Line 36: Line 48:
 * TutorialConflict - handling ["Merge"]s that need manual resolution  * TutorialConflict - handling [:Merge:merges] that need manual resolution
Line 38: Line 50:

----
CategoryTutorial

(you might first want to read UnderstandingMercurial)

A tutorial on using Mercurial

(Translations: [:ChineseTutorial:Chinese], [:FrenchTutorial:French], [:GermanTutorial:German], [:ItalianTutorial:Italian], [:JapaneseTutorial:Japanese], [:KoreanTutorial:Korean], [:BrazilianPortugueseTutorial:Brazilian Portuguese], [:SpanishTutorial:Spanish] )

This tutorial is an introduction to using Mercurial. We don't assume any particular background in using ["SCM"] software.

After you work through this tutorial, you should have a grasp of the following:

  • The basic concepts and commands you'll need to use Mercurial
  • How to use Mercurial in simple ways to contribute to a software project

It is also strongly recommended that you have a look at the Mercurial man pages [http://www.selenic.com/mercurial/hg.1.html hg(1)] and [http://www.selenic.com/mercurial/hgrc.5.html hgrc(5)], which are in the source tree as doc/hg.1.txt and doc/hgrc.5.txt.

1. How to read this tutorial

The formatting convention is simple. Command names and parameters are displayed in fixed font.

A line of input that you should type into your shell or command prompt is displayed in a fixed font, and the line will start with a $ character.

A line of output that you should expect Mercurial or your shell to display is displayed in a fixed font, but with no special character at the start of the line. 

$ this is a line of user input
this is a line of program output

We use the bash shell in all examples. The concepts remain the same for other Unix shells and the Windows cmd.exe, but the syntax of some operations may change. For example, ls in a Unix shell is roughly equivalent to dir under Windows, and Unix vi is similar to Windows edit.

2. Table of contents

CategoryTutorial

Tutorial (last edited 2013-09-02 17:41:09 by LeonardoPostacchini)