From: Bruno Haible <bruno@clisp.org>
To: "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: bug-gnulib@gnu.org
Subject: Re: bugs.llvm.org
Date: Thu, 30 Jan 2020 18:50:18 +0100 [thread overview]
Message-ID: <1597198.KK7d94p08v@omega> (raw)
In-Reply-To: <fa6c274d-d97b-add8-b55b-7b4bb279637b@gmx.de>
Tim Rühsen wrote:
> Sadly, bugs.llvm.org disabled self-registration. So they won't get a bug
> report from me (looks like they want to encapsulate from the rest of the
> world).
The text says: "New user self-registration is disabled due to spam.
For an account please email bugs-admin@lists.llvm.org with your e-mail
address and full name." In other words, you write a hand-written mail,
and someone adds your account manually. Same procedure as, for example,
for the bug tracker on dev.gnupg.org.
Bruno
prev parent reply other threads:[~2020-01-30 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 10:58 clang-10 warning in hash.c Tim Rühsen
2020-01-27 13:09 ` Bruno Haible
2020-01-27 20:16 ` Paul Eggert
2020-01-27 21:03 ` Bruno Haible
2020-01-28 2:08 ` Bruno Haible
2020-01-30 15:35 ` Tim Rühsen
2020-01-30 17:50 ` Bruno Haible [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1597198.KK7d94p08v@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=tim.ruehsen@gmx.de \
/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).