From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>, aldot@gcc.gnu.org
Subject: Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)
Date: Sun, 16 Apr 2023 21:34:47 +0200 [thread overview]
Message-ID: <E2AC71DE-FFE2-4B46-9504-8F05C6F9EADC@gmail.com> (raw)
In-Reply-To: <ZDlrZRD/iW/R5x+7@elastic.org>
On 14 April 2023 17:04:05 CEST, "Frank Ch. Eigler" <fche@elastic.org> wrote:
>OK, all done.
Works like a charm.
Thanks!
next prev parent reply other threads:[~2023-04-16 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 10:00 Bernhard Reutner-Fischer
2023-04-13 20:27 ` Frank Ch. Eigler
2023-04-14 7:45 ` Bernhard Reutner-Fischer
2023-04-14 15:04 ` Frank Ch. Eigler
2023-04-16 19:34 ` Bernhard Reutner-Fischer [this message]
2023-04-17 9:07 ` Mark Wielaard
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=E2AC71DE-FFE2-4B46-9504-8F05C6F9EADC@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=aldot@gcc.gnu.org \
--cc=fche@elastic.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).