From ea416f05b1c74f553721be58a5e7e5cb1cba48ce Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Fri, 16 Aug 2013 02:50:10 +0200 Subject: cloning repositories MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- using-git.texinfo | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) (limited to 'using-git.texinfo') diff --git a/using-git.texinfo b/using-git.texinfo index 71ef58b..ce906d3 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -53,6 +53,7 @@ Texts. A copy of the license is included in the section entitled * Getting started:: * Introduction:: * Branching out:: +* Collaborating:: * GNU Free Documentation License:: @end menu @@ -466,6 +467,34 @@ the files and make a new commit. +@node Collaborating +@chapter Collaborating + +@menu +* Cloning a repository:: +@end menu + + + +@node Cloning a repository +@section Cloning a repository + +The first thing you need to do in order +to begin collaboration is the clone the +repository: + +@example +git clone REPOSITORY -o upstream +@end example + +By including @command{-o upstream}, git +sets up the cloned repository as a +remote repository named `upstream'. + +If you want to access a branch in the +upstream repository, use +@code{upstream/BRANCH} as the branch name. + @node GNU Free Documentation License -- cgit v1.2.3-70-g09d2