From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Damian Rogers <damian@sudden-desu.net>
Subject: Re: Creating account for bug reporting
Date: Thu, 20 Jan 2022 10:22:53 -0500 [thread overview]
Message-ID: <Yel+Te+93N899UqL@elastic.org> (raw)
In-Reply-To: <0add76d040effcd1d9c096ccf1f196fadbe5abd0.camel@sudden-desu.net>
Hi -
> I would like to create an account to report a potential bug with
> binutils 2.37. Please let me know what further information is needed.
Created, thanks.
- FChE
prev parent reply other threads:[~2022-01-20 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:13 Damian Rogers
2022-01-20 15:22 ` Frank Ch. Eigler [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=Yel+Te+93N899UqL@elastic.org \
--to=fche@elastic.org \
--cc=damian@sudden-desu.net \
--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).