Skip to content

Commit 179c999

Browse files
committed
origin is not special admonition
1 parent b5676f5 commit 179c999

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

book/03-git-branching/1-git-branching.asc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -628,6 +628,12 @@ Let's say you have a Git server on your network at `git.ourcompany.com`.
628628
If you clone from this, Git automatically names it `origin` for you, pulls down all its data, creates a pointer to where its `master` branch is, and names it `origin/master` locally; and you can't move it.
629629
Git also gives you your own `master` branch starting at the same place as origin's `master` branch, so you have something to work from.
630630

631+
[NOTE]
632+
.``origin'' is not special
633+
====
634+
Just like the branch name ``master'' does not have any special meaning in Git, neither does ``origin''. While ``master'' is the default name for a starting branch when you run `git init` which is the only reason it's widely used, ``origin'' is the default name for a remote when you run `git clone`. If you run `git clone -o booyah` instead, then you will have `booyah/master` as your default remote branch.
635+
====
636+
631637
.Server and local repositories after cloning
632638
image::images/18333fig0322-tn.png[Server and local repositories after cloning.]
633639

0 commit comments

Comments
 (0)