From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20104 invoked by alias); 24 Jan 2020 15:47:40 -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 20041 invoked by uid 9007); 24 Jan 2020 15:47:39 -0000 Date: Fri, 24 Jan 2020 15:47:00 -0000 Message-ID: <20200124154739.20038.qmail@sourceware.org> From: rearnsha@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. dc50865bf99c3a2abf007bb15c011bdecc583413 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: b1bd21c81af3bc3098fca4293af164a6c6a4544a X-Git-Newrev: dc50865bf99c3a2abf007bb15c011bdecc583413 X-SW-Source: 2020/txt/msg00077.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 dc50865bf99c3a2abf007bb15c011bdecc583413 (commit) from b1bd21c81af3bc3098fca4293af164a6c6a4544a (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 dc50865bf99c3a2abf007bb15c011bdecc583413 Author: Richard Earnshaw Date: Fri Jan 24 15:22:16 2020 +0000 gitwrite: Move warning about not pushing to other users' spaces Move the warning about not pushing to other users' spaces to the introductory material for personal and vendor branches and adapt to cover vendor spaces as well. Minor tweaks to the original text. diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index b5d7ff3..97d6087 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -378,7 +378,7 @@ The GCC git repository is used by many people and the branch and tag namespace would become very polluted if all branches lived at the top-level naming space. To help minimise the amount of data that needs to be fetched the git repository on gcc.gnu.org supports -having personal and vendor branches that developers use to +having personal and vendor spaces that developers use to share their work. These are not pulled by default, but simple configuration steps can give access to them. @@ -391,7 +391,14 @@ configuration steps can give access to them. in refs/vendors/vendor-name/tags. -Scripts exist in the contrib directory to help manage these spaces. +

Personal and vendor spaces are controlled by the individual +user or vendor. Do not push changes to somebody else's space without +their express permission. Rather than pushing to somebody +else's branch, consider pushing to your own personal branch and having +collaborators pull from there. +

+ +

Scripts exist in the contrib directory to help manage these spaces.

contrib/gcc-git-customization.sh

@@ -436,12 +443,6 @@ you intend. The script contrib/git-add-user-branch.sh can be used to create a new personal branch which can be pushed and pulled from the users/me remote.

-

Personal spaces are controlled by the individual user. Do not push -changes to somebody else's space without their express permission. -(Rather than pushing to somebody else's personal branch, consider pushing -to your own personal branch and having collaborators pull from there.) -

-

The script also defines a few useful aliases that can be used with the repository:

----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) hooks/post-receive -- gcc-wwwdocs