public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Carlos O'Donell <carlos@systemhalted.org>, <iains.gcc@gmail.com>,
	<gnutools-advocacy@gcc.gnu.org>
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1810021946370.23779@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAGWvny=1fmtaad0ngA3Qk52X+TmU4BBt8p8YsJVyOenD12X9Bg@mail.gmail.com>

On Tue, 2 Oct 2018, David Edelsohn wrote:

> [Sorry if this is a duplicate.]
> 
> We initially can use Github pages.  Github pages allow custom domain
> names.  That would allow us to collaborate on the page.
> 
> As I mentioned to Carlos privately, I have registered gnutools.org and
> gnutoolchain.org.
> 
> Does anyone know who controls the gcc-mirror Github account?

I *think* gcc-mirror is an instance of an old GitHub feature where they 
would set up and maintain mirrors of external repositories (a service they 
no longer document or provide new instances of, instead expecting people 
who want mirrors to do their own push --mirror in a post-receive hook, see 
e.g. 
<https://stackoverflow.com/questions/11370239/creating-an-official-github-mirror>).  
So probably that account is controlled by GitHub.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2018-10-02 19:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  0:00 Iain Sandoe
2018-01-01  0:00 ` Carlos O'Donell
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` Joseph Myers [this message]
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` David Edelsohn
2018-01-01  0:00       ` Carlos O'Donell
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` David Edelsohn
2018-01-01  0:00             ` David Edelsohn
2018-01-01  0:00   ` Alexandre Oliva
2018-01-01  0:00     ` Carlos O'Donell
2018-01-01  0:00       ` Richard Stallman
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Alexandre Oliva
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` Alexandre Oliva
2018-01-01  0:00                 ` Richard Biener
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                     ` David Edelsohn
2018-01-01  0:00                       ` Alexandre Oliva
2018-01-01  0:00                         ` David Edelsohn
2018-01-01  0:00                           ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00               ` Richard Stallman
2018-01-01  0:00           ` Richard Stallman
2018-01-01  0:00       ` Alexandre Oliva

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=alpine.DEB.2.21.1810021946370.23779@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@systemhalted.org \
    --cc=dje.gcc@gmail.com \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    /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).