public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 5492d93acc449f465f4d8ae80d338f27ef067e3c Date: Thu, 23 Jan 2020 11:07:00 -0000 [thread overview] Message-ID: <20200123110708.128132.qmail@sourceware.org> (raw) 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 <rearnsha@arm.com> 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 <em>project</em> ../project master </pre></blockquote> +<h3 id="repolayout">Repository Layout</h3> + +<p>By default, a <code>git clone</code> 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.</p> + +<p>The following areas exist on the server:</p> +<ul> + <li><i>refs/heads/master</i> - The active development version of the + compiler.</li> + <li><i>refs/heads/releases/*</i> - Release branches.</li> + <li><i>refs/heads/devel/*</i> - topic-specific development branches + - see <a href="#devbranches">Active Development Branches</a>. + Branches and tags in this space may be moved to refs/dead once active + development is completed or abandoned.</li> + <li><i>refs/tags/*</i> - tags for all of the above branches.</li> + <li><i>refs/vendors/*/{heads,tags}/*</i> - 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.</li> + <li><i>refs/users/*/{heads,tags}/*</i> - personal developer branches and + tags. These are owned and maintained by the individual developer. + Non-fast-forward pushes are permitted on these branches.</li> + <li><i>refs/dead/heads/*</i> - completed or abandoned development + branches.</li> + <li><i>refs/meta/config</i> - local configuration data for the + commit hooks on the server.</li> + <li><i>refs/deleted/*/{heads,tags}/*</i> - old branches and tags + from the SVN repository that were deleted before the conversion to + git.</li> + <li><i>refs/git-svn-old/*</i> - various branches and tags from the + git-svn pre-conversion git mirror.</li> + <li><i>refs/git-old/*</i> - various branches and tags from the + git-svn pre-conversion git mirror that were local to that git + repository.</li> +</ul> + +<p>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:</p> + +<blockquote><pre> + 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 +</pre></blockquote> + +<p>which will place the dead branches in <code>remotes/origin/dead</code> + and the tags in <code>tags/dead</code>.</p> + +<p>You can use <code>git ls-remote</code> to get a complete list of +refs that the server holds.</p> + <h3 id="devbranches">Active Development Branches</h3> <ul> ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-23 11:07 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200123110708.128132.qmail@sourceware.org \ --to=rearnsha@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).