public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: redi@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f526c4724b183482fc7fe1a5ce78e1597fd1005f
Date: Fri, 24 Jan 2020 15:11:00 -0000	[thread overview]
Message-ID: <20200124151151.39839.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  f526c4724b183482fc7fe1a5ce78e1597fd1005f (commit)
      from  b9024cd93b5a5aa7de629232e0631c1fbdac4544 (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 f526c4724b183482fc7fe1a5ce78e1597fd1005f
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Jan 24 15:00:57 2020 +0000

    Adjust docs on personal Git branches

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 55667a2d..b5d7ff35 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -436,6 +436,12 @@ you intend.  The script <code>contrib/git-add-user-branch.sh</code>
 can be used to create a new personal branch which can be pushed and
 pulled from the <i>users/me</i> remote.</p>
 
+<p><em>Personal spaces are controlled by the individual user.  Do not push
+changes to somebody else's space without their express permission.</em>
+(Rather than pushing to somebody else's personal branch, consider pushing
+to your own personal branch and having collaborators pull from there.)
+</p>
+
 <p>The script also defines a few useful aliases that can be used with the
 repository:</p>
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gitwrite.html | 6 ++++++
 1 file changed, 6 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-24 15:11 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=20200124151151.39839.qmail@sourceware.org \
    --to=redi@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: link
Be 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).