From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Etienne Champetier <champetier.etienne@gmail.com>
Subject: Re: account for glibc bug report
Date: Wed, 24 Aug 2022 13:07:37 +0200 [thread overview]
Message-ID: <e15d2002513a7e8d8567132cfed3803bd9cd0d3a.camel@klomp.org> (raw)
In-Reply-To: <CAOdf3gosRhOGxN=jehuZJ6k5mt2TbBKi7VV3SNX5fM5Cx1vJ+Q@mail.gmail.com>
Hi Etienne,
On Wed, 2022-08-24 at 06:57 -0400, Etienne Champetier via Overseers
wrote:
> I would like to report a bug to glibc maintainers (weird bug in
> regex)
A 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
prev parent reply other threads:[~2022-08-24 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 10:57 Etienne Champetier
2022-08-24 11:07 ` Mark Wielaard [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=e15d2002513a7e8d8567132cfed3803bd9cd0d3a.camel@klomp.org \
--to=mark@klomp.org \
--cc=champetier.etienne@gmail.com \
--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).