From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128178 invoked by alias); 23 Jan 2020 11:07:08 -0000 Mailing-List: contact gcc-cvs-wwwdocs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-cvs-wwwdocs-owner@gcc.gnu.org Received: (qmail 128135 invoked by uid 9007); 23 Jan 2020 11:07:08 -0000 Date: Thu, 23 Jan 2020 11:07:00 -0000 Message-ID: <20200123110708.128132.qmail@sourceware.org> From: rearnsha@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 5492d93acc449f465f4d8ae80d338f27ef067e3c X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: a3bcd42bc345f3f1f45f93a3c95b954c9868586f X-Git-Newrev: 5492d93acc449f465f4d8ae80d338f27ef067e3c X-SW-Source: 2020/txt/msg00066.txt This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 5492d93acc449f465f4d8ae80d338f27ef067e3c (commit) from a3bcd42bc345f3f1f45f93a3c95b954c9868586f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 5492d93acc449f465f4d8ae80d338f27ef067e3c Author: Richard Earnshaw Date: Thu Jan 23 11:06:28 2020 +0000 Document the gcc git repository layout The GCC git repository makes use of some non-standard refs so that by default only the most active and useful branches and tags are fetched by a git clone. This patch documents the additional branch and tag spaces that exist on the server. diff --git a/htdocs/git.html b/htdocs/git.html index 6100146..66d68eb 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -197,6 +197,61 @@ To create a worktree for a new project branch based on master, do git worktree add -b project ../project master +

Repository Layout

+ +

By default, a git clone operation will only fetch the +main development, release branches and their associated tags from the +server. This will be sufficient for most users, but a number of +additional branches can also be fetched if necessary.

+ +

The following areas exist on the server:

+
    +
  • refs/heads/master - The active development version of the + compiler.
  • +
  • refs/heads/releases/* - Release branches.
  • +
  • refs/heads/devel/* - topic-specific development branches + - see Active Development Branches. + Branches and tags in this space may be moved to refs/dead once active + development is completed or abandoned.
  • +
  • refs/tags/* - tags for all of the above branches.
  • +
  • refs/vendors/*/{heads,tags}/* - vendor-specific branches and + tags. These are owned and maintained by the respective + vendor, but made available publicly. Non-fast-forward pushes + are permitted on these branches.
  • +
  • refs/users/*/{heads,tags}/* - personal developer branches and + tags. These are owned and maintained by the individual developer. + Non-fast-forward pushes are permitted on these branches.
  • +
  • refs/dead/heads/* - completed or abandoned development + branches.
  • +
  • refs/meta/config - local configuration data for the + commit hooks on the server.
  • +
  • refs/deleted/*/{heads,tags}/* - old branches and tags + from the SVN repository that were deleted before the conversion to + git.
  • +
  • refs/git-svn-old/* - various branches and tags from the + git-svn pre-conversion git mirror.
  • +
  • refs/git-old/* - various branches and tags from the + git-svn pre-conversion git mirror that were local to that git + repository.
  • +
+ +

You can download any of the additional branches by adding a suitable +fetch specification to your local copy of the git repostiory. For +example, if your remote is called 'origin' (the default with git +clone) you can add the 'dead' development branches by running:

+ +
+    git config --add remote.origin.fetch "+refs/dead/heads/*:refs/remotes/origin/dead/*"
+    git config --add remote.origin.fetch "+refs/dead/tags/*:refs/tags/dead/*"
+    git fetch origin
+
+ +

which will place the dead branches in remotes/origin/dead + and the tags in tags/dead.

+ +

You can use git ls-remote to get a complete list of +refs that the server holds.

+

Active Development Branches

    ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) hooks/post-receive -- gcc-wwwdocs