public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31098] Typo-squatted Core Toolchain Infrastructure domain names pointing at Sourcware?
Date: Thu, 30 Nov 2023 12:38:29 +0000	[thread overview]
Message-ID: <bug-31098-14326-GRx8XPXF6e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31098-14326@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31098

--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Mark Wielaard from comment #1)
> Heay ancient history. You might have forgotten that we originally registered
> gnu.toolchain.dev for the GNU Tools Assembly but we ended up using the
> gnu.tools domain for that. Then when we started the GNU Toolchain
> Infrastructure discussions a couple of years back we repurposed it to point
> at sourceware.org.

Thanks for the context Mark!

Yes, the GNU Assembly is currently using gnu.tools.

I had forgotten that "gnu.toolchain.dev" was registered for that use too e.g.
GNU Assembly.

For this particular issue I wanted to make sure that nobody was paying for a
domain that they didn't want and that they thought would be useful to prevent
typo-squatting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2023-11-30 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 17:16 [Bug Infrastructure/31098] New: " carlos at redhat dot com
2023-11-29 17:48 ` [Bug Infrastructure/31098] " mark at klomp dot org
2023-11-30 12:38 ` carlos at redhat dot com [this message]

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=bug-31098-14326-GRx8XPXF6e@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=overseers@sourceware.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).