On 23/01/20 16:23 +0000, Richard Earnshaw (lists) wrote:
On 21/01/2020 18:58, Richard Earnshaw (lists) wrote:
This patch documents some of the scripts that I've published for
managing the personal and vendor spaces on the server. It also
covers some of the other features that those scripts enable, so that
it's all in one place. This is a complete rewrite of the material I
had written previously since before we did not have these scripts to
make use of.
I've not filled in the documentation for gcc-descr and gcc-undescr,
Jakub has agreed to provide that at a later date.
R.
I've pushed this. I think it's better to have this in than nothing at
all. We can iterate on it as required.
I've pushed the attached fix for a couple of typos.
Do we want to repeat the "do not push changes to that space without
their express permission" for user branches? There are no access
checks to prevent it, but I hsouldn't be changing things in your
branches without your permission.
Finally, why does this qualify it as "If you have multiple clones"?
<p>If you have multiple clones of the gcc repository you can fetch
updates from your personal space by running
<code>git fetch me</code>
Isn't that the right command even if you only have one clone?
commit 182ab16b43b0b40b985e0678891b29debef2c9a2
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Fri Jan 24 10:59:14 2020 +0000
Fix typos in gitwrite.html
diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index ad073b53..c0fe8526 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -391,7 +391,7 @@ configuration steps can give access to them.
in <code>refs/vendors/<i>vendor-name</i>/tags</code>.</li>
</ul>
-Scripts exist the contrib directory to help manage these spaces.
+Scripts exist in the contrib directory to help manage these spaces.
<h3>contrib/gcc-git-customization.sh</h3>
@@ -413,7 +413,7 @@ some aliases that might be useful when developing GCC. The script will
work this out based on the URL used to fetch from the git server, or
fall back to your local user name if that fails. Using this name
on the server for your personal space ensures that your branches will
- not conflict with anybody elses.</li>
+ not conflict with anybody else's.</li>
<li><i>The prefix to use for your personal branches</i> - the default is
<code>me</code>, but you can change this if you prefer. The script
will add configuration information to allow local branches that