From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Ivan G." <nekotekina@gmail.com>
Subject: Re: Creating an account at bugzilla
Date: Mon, 24 Jan 2022 19:55:48 -0500 [thread overview]
Message-ID: <Ye9KlDOCQZNg+hO2@elastic.org> (raw)
In-Reply-To: <4cf28506-1794-027e-1e0a-a77ad4659a2a@gmail.com>
Hi -
> Hello, I want to report a bug in objdump utility.
Thanks, done, enjoy.
- FChE
prev parent reply other threads:[~2022-01-25 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 0:52 Ivan G.
2022-01-25 0:55 ` 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=Ye9KlDOCQZNg+hO2@elastic.org \
--to=fche@elastic.org \
--cc=nekotekina@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).