git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] glossary: explain "master" and "origin"

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 10, 2006, 21:26 UTC
Message-ID
<Pine.LNX.4.63.0601102226130.649@wbgn013.biozentrum.uni-wuerzburg.de>

If you are a long time git user/developer, you forget that to a new git user, these words have not the same meaning as to you.

Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
---
 Documentation/glossary.txt |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index 2331be5..4ef7d2a 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -111,6 +111,17 @@ branch::
 	a particular revision, which is called the branch head. The
 	branch heads are stored in `$GIT_DIR/refs/heads/`.
 
+master::
+	The default branch. Whenever you create a git repository, a branch
+	named "master" is created, and becomes the active branch. In most
+	cases, this contains the local development.
+
+origin::
+	The default upstream branch. Most projects have one upstream 
+        project which is tracked, and augmented with local changes which
+        eventually get merged back. You never commit to this branch,
+	unless you are maintaining the upstream project.
+
 ref::
 	A 40-byte hex representation of a SHA1 pointing to a particular
 	object. These may be stored in `$GIT_DIR/refs/`.
Next: J. Bruce Fields
Message 1 of 6 in “glossary: explain "master" and "origin"”
  1. glossary: explain "master" and "origin"Johannes Schindelin, Jan 10, 2006
  2. J. Bruce FieldsJan 10, 2006
  3. Johannes SchindelinJan 10, 2006
  4. Junio C HamanoJan 11, 2006
  5. waltJan 10, 2006
  6. waltJan 10, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.