From: Carolyn Hughes <crh883@utulsa.edu>
To: overseers@sourceware.org
Subject: Bug Report
Date: Thu, 31 Mar 2022 12:58:16 -0500 [thread overview]
Message-ID: <ae3fb92c-055f-40c8-9e9d-1957d1d32768@Spark> (raw)
In-Reply-To: <e6d77ef5-9955-43ca-bd4f-3a24f664cd5d@Spark>
Hi, I am trying to make an account so that I can make a bug report for the bfd library, but am getting an error saying account creation is restricted. Can you help me?
next parent reply other threads:[~2022-03-31 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e6d77ef5-9955-43ca-bd4f-3a24f664cd5d@Spark>
2022-03-31 17:58 ` Carolyn Hughes [this message]
2022-03-31 18:17 ` Mark Wielaard
2022-03-31 18:18 ` Carolyn Hughes
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=ae3fb92c-055f-40c8-9e9d-1957d1d32768@Spark \
--to=crh883@utulsa.edu \
--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).