public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Patrick O'Neill" <patrick@rivosinc.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: New Account
Date: Thu, 20 Jan 2022 15:40:23 -0800	[thread overview]
Message-ID: <CAHwnyx2TLfA4mFbv16wbg_2EjZS4WgUJ1Kxo=U6MVW-kMj-bXg@mail.gmail.com> (raw)
In-Reply-To: <YentfV4yZursabUp@wildebeest.org>

Thank you!

On Thu, Jan 20, 2022 at 3:17 PM Mark Wielaard <mark@klomp.org> wrote:

> Hi Patrick,
>
> On Thu, Jan 20, 2022 at 03:12:44PM -0800, Patrick O'Neill via Overseers
> wrote:
> > I'm trying to sign up for a new account on sourceware, but account signup
> > is restricted.
>
> An bugzilla account has been created for you. You should have gotten
> an email about it. You can activate your account through the
> Forgot/Reset Password link.
>
> Cheers,
>
> Mark
>
>

  reply	other threads:[~2022-01-20 23:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 23:12 Patrick O'Neill
2022-01-20 23:17 ` Mark Wielaard
2022-01-20 23:40   ` Patrick O'Neill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-12 10:57 New account lisawi
2022-08-12 14:59 ` Mark Wielaard
2022-07-05 17:08 New Account Reto Schneider
2022-07-05 17:35 ` Mark Wielaard
2022-05-31 22:14 Jacob Kane
2022-06-01  7:01 ` Mark Wielaard
2022-04-29 12:14 New account Artur Łącki
2022-04-30  9:54 ` Mark Wielaard
2021-12-05 22:53 Evgeny Vereshchagin
2021-12-06  7:27 ` Mark Wielaard
2017-05-07 21:42 Ondřej Majerech
2017-01-26 20:46 paul
2011-12-15 18:21 Jeff Law
2000-12-30  6:08 new account Ulrich Drepper
2000-06-15 16:45 ` Ulrich Drepper
2000-12-30  6:08 ` Tom Tromey
2000-06-15 18:29   ` Tom Tromey
2000-12-30  6:08   ` Ulrich Drepper
2000-06-15 20:23     ` Ulrich Drepper
2000-12-30  6:08     ` Tom Tromey
2000-06-15 21:32       ` Tom Tromey

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='CAHwnyx2TLfA4mFbv16wbg_2EjZS4WgUJ1Kxo=U6MVW-kMj-bXg@mail.gmail.com' \
    --to=patrick@rivosinc.com \
    --cc=mark@klomp.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).