This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] wwwdocs: document scripts to access personal and vendor spaces
On 24/01/2020 11:04, Jonathan Wakely wrote:
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.
Absolutely. I guess I took this as read in the personal spaces.
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?
Well, if you only have one clone, why would you need to pull branches
from upstream that you pushed yourself? In fact, why would you even
need to push them in that case, unless it's for backup? ... and if
you're restoring your backup, then that's a new clone. You might
temporally have only only one clone, but across all time you have more
than one.
It's pedantry, though, so feel free to re-word it.
Thanks for the tweaks, anyway.
R.